Triple
T30161481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LONDON TERMINALS (on tickets) |
E766676
|
entity |
| Predicate | isGroupDestination |
P168507
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LONDON TERMINALS (on tickets), isGroupDestination, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGroupDestination Context triple: [LONDON TERMINALS (on tickets), isGroupDestination, true]
-
A.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
B.
isDestinationBased
Indicates that something is determined, organized, or classified according to its destination.
-
C.
isTypeOfDestination
Indicates that one entity serves as a classification or category describing the kind or type of destination that another entity represents.
-
D.
hasPrivateDestination
Indicates that an entity is associated with a destination that is not publicly accessible or is intended for restricted/private use.
-
E.
hasDestinationRegion
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
- F. None of above. chosen
Provenance (4 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67edb30d8819097a9f90443428fc2 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:21 p.m.