Triple
T21714454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit Airport |
E535986
|
entity |
| Predicate | pushpin map caption |
P65680
|
FINISHED |
| Object | Location of airport in Delaware |
—
|
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: Location of airport in Delaware | Statement: [Summit Airport, pushpin map caption, Location of airport in Delaware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pushpin map caption Context triple: [Summit Airport, pushpin map caption, Location of airport in Delaware]
-
A.
mapCaption
Indicates that the value is a textual caption or label describing the associated map.
-
B.
pushpinCaption
chosen
Indicates the descriptive text label associated with a pushpin marker, typically explaining or identifying what the marker represents.
-
C.
pushpinMapCountry
Indicates the country whose map is used as the background or reference area for placing a pushpin-style location marker.
-
D.
mapLabel
Indicates that a label or name is assigned to a map or mapped entity for identification or display.
-
E.
mappingNote
Indicates a descriptive note or comment that provides additional information about a specific mapping or correspondence between entities.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5369be88190bafc10863d4d1bd7 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.