Triple
T8416376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airstrip One |
E198738
|
entity |
| Predicate | permanentStateOf |
P32534
|
FINISHED |
| Object | war |
—
|
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: war | Statement: [Airstrip One, permanentStateOf, war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentStateOf Context triple: [Airstrip One, permanentStateOf, war]
-
A.
permanence
chosen
Indicates that a state, condition, or relationship continues to hold over time without significant change or interruption.
-
B.
permanentAdoption
Indicates a lasting, legally recognized adoption relationship in which the adoptee becomes a permanent member of the adopter’s family.
-
C.
permanentServiceBegan
Indicates that an entity’s ongoing or long-term service or role officially started at a specific point in time.
-
D.
ultimateState
Indicates the final or end condition that an entity or process ultimately reaches after all preceding stages or transitions.
-
E.
persistsAfter
Indicates that one state, condition, or effect continues to exist after a specified event, time point, or other state has occurred or ended.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.