Triple
T13891636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercidades |
E333984
|
entity |
| Predicate | serviceLevelComparedToRegional |
P111901
|
FINISHED |
| Object | faster than regional trains |
—
|
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: faster than regional trains | Statement: [Intercidades, serviceLevelComparedToRegional, faster than regional trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceLevelComparedToRegional Context triple: [Intercidades, serviceLevelComparedToRegional, faster than regional trains]
-
A.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
-
B.
serviceLevelComparedToEconomy
Indicates how the level or quality of service compares relative to an economy (baseline) service level.
-
C.
regionalServiceOperational
Indicates that a service is currently functioning and available within a specified geographic region.
-
D.
serviceBranchLevel
Indicates the hierarchical level or tier within a service branch at which an entity operates or is classified.
-
E.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
- F. None of above. chosen
Provenance (4 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a537d4819093c2bae2a244816a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:15 p.m.