Triple
T4059965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBK (Amtrak) |
E84785
|
entity |
| Predicate | schedulingSystem |
P51688
|
FINISHED |
| Object | Amtrak 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: Amtrak timetable system | Statement: [NBK (Amtrak), schedulingSystem, Amtrak timetable system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingSystem Context triple: [NBK (Amtrak), schedulingSystem, Amtrak timetable system]
-
A.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
B.
usedInSchedulingSystems
chosen
Indicates that something is employed as a component or mechanism within scheduling systems to plan, allocate, or manage tasks, resources, or time.
-
C.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
D.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
E.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.