Triple
T3256691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T2 Inner West & Leppington Line |
E68312
|
entity |
| Predicate | hasTimetable |
P28039
|
FINISHED |
| Object | published by Sydney 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: published by Sydney Trains | Statement: [T2 Inner West & Leppington Line, hasTimetable, published by Sydney Trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetable Context triple: [T2 Inner West & Leppington Line, hasTimetable, published by Sydney Trains]
-
A.
hasTimetableProvider
chosen
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
B.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
C.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
D.
hasDayStudents
Indicates that an educational institution has students who attend during the day but do not reside on campus.
-
E.
hasInductionSchedule
Indicates that an entity is associated with a defined plan or timetable for its induction or onboarding process.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf68b280819087c302d454490c03 |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.