Triple
T214575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Positive Train Control |
E4790
|
entity |
| Predicate | hasDeadline |
P8546
|
FINISHED |
| Object | original implementation deadline 2015 |
—
|
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: original implementation deadline 2015 | Statement: [Positive Train Control, hasDeadline, original implementation deadline 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeadline Context triple: [Positive Train Control, hasDeadline, original implementation deadline 2015]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
D.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
E.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c32ae208190a03d504ef43ea659 |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.