Triple
T29683635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementary |
E751022
|
entity |
| Predicate | followedByTimeslotChange |
P190488
|
FINISHED |
| Object | Sunday |
—
|
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: Sunday | Statement: [Elementary, followedByTimeslotChange, Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByTimeslotChange Context triple: [Elementary, followedByTimeslotChange, Sunday]
-
A.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
-
B.
replacedByInTimetables
Indicates that one service or entity is superseded by another in official timetables from a certain point in time.
-
C.
followedByAdaptation
Indicates that one work, event, or version is succeeded by another that adapts or reinterprets it.
-
D.
followedByRelocationOf
Indicates that one event, state, or condition is immediately or subsequently succeeded by a relocation of an entity to a different place or position.
-
E.
followedByStation
Indicates that one station directly succeeds another in a sequence, such as along a transit line or route.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: April 28, 2026, 7:12 p.m.