Triple
T5401980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seville Metro |
E120797
|
entity |
| Predicate | fareZoneCount |
P57453
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Seville Metro, fareZoneCount, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareZoneCount Context triple: [Seville Metro, fareZoneCount, 3]
-
A.
fareZoneUsage
Indicates how a fare zone is applied or utilized within a transportation or pricing context.
-
B.
numberOfZones
chosen
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
C.
fareZoneHierarchyPosition
Indicates the relative level or rank of a fare zone within a hierarchical fare zone structure.
-
D.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
E.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.