Triple
T23296279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Distancia |
E590179
|
entity |
| Predicate | typicalServiceDistance |
P93586
|
FINISHED |
| Object | 100–300 km |
—
|
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: 100–300 km | Statement: [Media Distancia, typicalServiceDistance, 100–300 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServiceDistance Context triple: [Media Distancia, typicalServiceDistance, 100–300 km]
-
A.
typicalLinkDistance
chosen
Indicates the usual or characteristic distance that typically separates two linked or related entities.
-
B.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
-
C.
hasApproximateDrivingDistanceFrom
Indicates that one entity is located at an estimated or approximate driving distance from another entity, typically measured along road routes rather than as a precise or exact value.
-
D.
typicalOffPeakServiceTo
Indicates the usual or standard off-peak (non-peak time) service pattern that operates to a given destination.
-
E.
isFartherFromCityCenterThan
Indicates that one location is at a greater distance from the city center than another location.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cec9e88190b83cfd53a6455e0f |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:03 p.m.