Triple
T19419837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combe railway station |
E485818
|
entity |
| Predicate | hasTimetablePoster |
P135810
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Combe railway station, hasTimetablePoster, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetablePoster Context triple: [Combe railway station, hasTimetablePoster, yes]
-
A.
hasTimetableInformation
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
B.
hasTimetableProvider
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
C.
hasFilmPoster
Indicates that one entity serves as the film poster associated with another film entity.
-
D.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
-
E.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63213b6ec8190b89982b554a0f6e7 |
completed | April 20, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.