Triple
T6247546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lou |
E139755
|
entity |
| Predicate | combatContext |
P61941
|
FINISHED |
| Object | cooperative shooter encounters |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: cooperative shooter encounters | Statement: [Lou, combatContext, cooperative shooter encounters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatContext Context triple: [Lou, combatContext, cooperative shooter encounters]
-
A.
militaryContext
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
-
B.
combatRelated
chosen
Indicates that the entities are connected through participation in, involvement with, or direct association to combat or military conflict.
-
C.
combatOrNonCombat
Indicates whether an entity is involved in combat activities or is in a non-combat role or situation.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631f511c81908d413320efdce42e |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.