Triple
T35790542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lights over Phoenix |
E1034680
|
entity |
| Predicate | officialExplanationBy |
P86112
|
FINISHED |
| Object | U.S. military |
—
|
NE NERFINISHED |
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: U.S. military | Statement: [Lights over Phoenix, officialExplanationBy, U.S. military]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialExplanationBy Context triple: [Lights over Phoenix, officialExplanationBy, U.S. military]
-
A.
hasOfficialExplanation
Indicates that an entity is accompanied by an authoritative or formally recognized explanation clarifying its reason, cause, or details.
-
B.
officialJustification
chosen
Indicates the formally stated reason or rationale that an authority or institution gives to legitimize an action, decision, or policy.
-
C.
explanation
Indicates that one entity provides a reason, clarification, or justification for another entity or event.
-
D.
officialFrom
Indicates that a person holds or held an official position representing or originating from a specified place, organization, or jurisdiction.
-
E.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:06 p.m.