Triple
T24952064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal D |
E624366
|
entity |
| Predicate | hasConcourseDesignation |
P1656
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [Terminal D, hasConcourseDesignation, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcourseDesignation Context triple: [Terminal D, hasConcourseDesignation, D]
-
A.
hasConcourse
chosen
Indicates that an entity includes, is connected to, or is served by a concourse area (such as a passageway or central hall).
-
B.
hasConcourseLevel
Indicates that an entity possesses or is associated with a specific concourse level within a building or facility.
-
C.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
D.
hasBDDesignation
Indicates that an entity has been assigned a specific BD (Business Development or similar domain-specific) designation or classification.
-
E.
hasDevelopmentDesignation
Indicates that an entity is assigned a specific development-related status, category, or designation within a development process or framework.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 18, 2026, 5:57 a.m.