Triple
T14157689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal E |
E350854
|
entity |
| Predicate | hasBusBoarding |
P63715
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Terminal E, hasBusBoarding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusBoarding Context triple: [Terminal E, hasBusBoarding, yes]
-
A.
hasBoardingType
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
B.
isBoarding
Indicates that an entity is in the process of getting onto or entering a vehicle, vessel, or similar mode of transport.
-
C.
hasBoardingOption
chosen
Indicates that an entity offers or is associated with a particular way or method by which passengers or items can board or be taken on.
-
D.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
E.
hasBoardingAreaFor
Indicates that one entity provides or contains a designated area where passengers can board another entity (such as a vehicle or vessel).
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61377de48190a3470d28f0edd34a |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:58 a.m.