Triple
T4428765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuremberg public transport network |
E95272
|
entity |
| Predicate | timetableSystem |
P15775
|
FINISHED |
| Object | integrated timetable system |
—
|
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: integrated timetable system | Statement: [Nuremberg public transport network, timetableSystem, integrated timetable system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timetableSystem Context triple: [Nuremberg public transport network, timetableSystem, integrated timetable system]
-
A.
hasTimetableProvider
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
B.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
C.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
D.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
E.
timeSystem
chosen
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35568767c819084d5e18b56a4745e |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.