Triple

T34492894
Position Surface form Disambiguated ID Type / Status
Subject Brown Field Municipal Airport E885517 entity
Predicate runway P1654 FINISHED
Object Runway 8L/26R
Runway 8L/26R is a primary paved runway at Brown Field Municipal Airport in San Diego, California, used mainly for general aviation and cross-border operations.
E2217005 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 8L/26R | Statement: [Brown Field Municipal Airport, runway, Runway 8L/26R]
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 8L/26R
Triple: [Brown Field Municipal Airport, runway, Runway 8L/26R]
Generated description
Runway 8L/26R is a primary paved runway at Brown Field Municipal Airport in San Diego, California, used mainly for general aviation and cross-border operations.

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_69f349cafcec8190997b45b3fdc16c27 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71cf042c48190ab0518d9e16a0322 completed May 3, 2026, 10:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a4035ee0b0481908be6705df4b332ef completed June 27, 2026, 8:43 p.m.
NEDg Description generation batch_6a4036e16c3481908e2e716c308a16c9 completed June 27, 2026, 8:47 p.m.
NED2 Entity disambiguation (via description) batch_6a4037c3080881908a677ca5eeff99bf completed June 27, 2026, 8:51 p.m.
Created at: May 1, 2026, 2:01 a.m.