Triple

T27694728

Position	Surface form	Disambiguated ID	Type / Status
Subject	Runway 15/33	`E698260`	entity
Predicate	hasRunwayEnd	`P8863`	FINISHED
Object	Runway 33 Runway 33 is one end of a bidirectional airport runway, typically aligned on a magnetic heading of approximately 330 degrees for aircraft takeoffs and landings.	`E1942376`	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 33 | Statement: [Runway 15/33, hasRunwayEnd, Runway 33]

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 33
Triple: [Runway 15/33, hasRunwayEnd, Runway 33]

Generated description

Runway 33 is one end of a bidirectional airport runway, typically aligned on a magnetic heading of approximately 330 degrees for aircraft takeoffs and landings.

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_69ef590ea74081908f0cd7500d85fa27`	completed	April 27, 2026, 12:39 p.m.
NER	Named-entity recognition	`batch_69f6359e3d3c81909814e2f0a7fb0ea9`	completed	May 2, 2026, 5:34 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a291802ada08190902290203bade01b`	completed	June 10, 2026, 7:53 a.m.
NEDg	Description generation	`batch_6a29197be90c8190bba41e7a1a7f9222`	completed	June 10, 2026, 7:59 a.m.
NED2	Entity disambiguation (via description)	`batch_6a291a7f7804819099458886138be398`	completed	June 10, 2026, 8:04 a.m.

Created at: April 27, 2026, 2:53 p.m.