Triple
T25583795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Gateway Station |
E641323
|
entity |
| Predicate | busOperatorPlanned |
P158872
|
FINISHED |
| Object | Charlotte Area Transit System |
—
|
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: Charlotte Area Transit System | Statement: [Charlotte Gateway Station, busOperatorPlanned, Charlotte Area Transit System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busOperatorPlanned Context triple: [Charlotte Gateway Station, busOperatorPlanned, Charlotte Area Transit System]
-
A.
busOperatorPlanned
chosen
Indicates that an entity is designated or scheduled to operate a bus service according to a plan.
-
B.
transportPlanned
Indicates that an arrangement has been made for something or someone to be transported from one place to another.
-
C.
plannedTransit
Indicates that a transit or trip has been scheduled or arranged to occur, but has not yet taken place.
-
D.
transportationPlanned
Indicates that an arrangement has been made for someone or something to be transported from one place to another.
-
E.
stationPlanned
Indicates that a station is intended or scheduled to be built or established in the future.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9675ae88190a09942a3a71be3ab |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:14 p.m.