Triple

T25379170
Position Surface form Disambiguated ID Type / Status
Subject Marine Corps Air Station Futenma E631334 entity
Predicate hasRunway P105 FINISHED
Object Runway 18/36
Runway 18/36 is the primary north–south oriented runway used for military aviation operations at Marine Corps Air Station Futenma in Okinawa, Japan.
E1774032 NE 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: Runway 18/36 | Statement: [Marine Corps Air Station Futenma, hasRunway, Runway 18/36]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Runway 18/36
Triple: [Marine Corps Air Station Futenma, hasRunway, Runway 18/36]
Generated description
Runway 18/36 is the primary north–south oriented runway used for military aviation operations at Marine Corps Air Station Futenma in Okinawa, Japan.

Provenance (5 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_69e75a8c50788190aabaa9f96710fc43 completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f55e5e4b0081909b64940d85d636f5 completed May 2, 2026, 2:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a12bbafcd508190aadd66053104a003 completed May 24, 2026, 8:49 a.m.
NEDg Description generation batch_6a12bc5e92b08190a2a7f60630f6d0ff completed May 24, 2026, 8:52 a.m.
NED2 Entity disambiguation (via description) batch_6a12bcd0c164819098f637afcad01642 completed May 24, 2026, 8:54 a.m.
Created at: April 21, 2026, 1:46 p.m.