Triple
T29527509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 15, Shuttle Landing Facility |
E749106
|
entity |
| Predicate | sharesPhysicalStripWith |
P23812
|
FINISHED |
| Object | Runway 33, Shuttle Landing Facility |
—
|
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: Runway 33, Shuttle Landing Facility | Statement: [Runway 15, Shuttle Landing Facility, sharesPhysicalStripWith, Runway 33, Shuttle Landing Facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPhysicalStripWith Context triple: [Runway 15, Shuttle Landing Facility, sharesPhysicalStripWith, Runway 33, Shuttle Landing Facility]
-
A.
sharesCorridorWith
Indicates that two entities are located along or connected by the same corridor or passageway.
-
B.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
C.
sharesAreaWith
chosen
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 28, 2026, 4:48 p.m.