Triple
T1676967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L86 LSW |
E36251
|
entity |
| Predicate | shoulderFired |
P31643
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [L86 LSW, shoulderFired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoulderFired Context triple: [L86 LSW, shoulderFired, yes]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
firstShotsFiredBy
Indicates which party or entity initiated a conflict or incident by discharging the first shots.
-
C.
associatedWithMissile
Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
-
D.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
E.
surrenderEvent
Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
- F. None of above. chosen
Provenance (4 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab271be3f4819091adcd745dec8159 |
completed | March 6, 2026, 7:12 p.m. |
Created at: March 4, 2026, 7:29 p.m.