Triple
T29349040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Wood |
E744250
|
entity |
| Predicate | travelZoneType |
P117758
|
FINISHED |
| Object | London Travelcard zone |
—
|
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: London Travelcard zone | Statement: [Harold Wood, travelZoneType, London Travelcard zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelZoneType Context triple: [Harold Wood, travelZoneType, London Travelcard zone]
-
A.
travelZone
chosen
Indicates a relationship where an entity is located in, moves within, or is permitted to move within a specified geographic or regulatory area.
-
B.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
travelScope
Indicates the extent or range within which travel is allowed, intended, or applicable for an entity or activity.
-
D.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
E.
regionOfTour
Indicates that a specified geographic or administrative region is the location or scope within which a particular tour takes place.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 2:05 p.m.