Triple
T38161146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport for London rail services |
E953020
|
entity |
| Predicate | hasZoneCoverage |
P6793
|
FINISHED |
| Object | Travelcard Zone 1 |
—
|
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: Travelcard Zone 1 | Statement: [Transport for London rail services, hasZoneCoverage, Travelcard Zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZoneCoverage Context triple: [Transport for London rail services, hasZoneCoverage, Travelcard Zone 1]
-
A.
hasAreaOfCoverage
Indicates that an entity provides services, influence, or applicability within a specified geographic or conceptual region.
-
B.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
hasProtectedAreaCoverage
Indicates that a specified portion or extent of an area falls within officially designated protected areas.
-
D.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
E.
hasZoneStatus
Indicates that a specified zone currently possesses a particular status or condition.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.