Triple
T1284583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pall Mall, London |
E27404
|
entity |
| Predicate | transportZone |
P17300
|
FINISHED |
| Object | London fare zone 1 |
—
|
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 fare zone 1 | Statement: [Pall Mall, London, transportZone, London fare zone 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportZone Context triple: [Pall Mall, London, transportZone, London fare zone 1]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
D.
zoneManagedFrom
Indicates that a particular zone or area is administered, controlled, or overseen from a specified location or managing entity.
-
E.
publicTransportZone
chosen
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b6dda48190a2e79084adea6ec1 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.