Triple
T30068724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tottenham Hale Retail Park |
E764113
|
entity |
| Predicate | typicalVisitorModeOfTransport |
P70707
|
FINISHED |
| Object | car |
—
|
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: car | Statement: [Tottenham Hale Retail Park, typicalVisitorModeOfTransport, car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVisitorModeOfTransport Context triple: [Tottenham Hale Retail Park, typicalVisitorModeOfTransport, car]
-
A.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
B.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
C.
hasPrimaryTransportationMode
chosen
Indicates the main or most frequently used mode of transportation associated with an entity.
-
D.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
E.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
Created at: April 29, 2026, 7 p.m.