Triple
T4730984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirling–Alloa–Kincardine line |
E105005
|
entity |
| Predicate | reopenedFor |
P59082
|
FINISHED |
| Object | passenger traffic |
—
|
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: passenger traffic | Statement: [Stirling–Alloa–Kincardine line, reopenedFor, passenger traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedFor Context triple: [Stirling–Alloa–Kincardine line, reopenedFor, passenger traffic]
-
A.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
B.
reopenedPartially
Indicates that an entity that was previously closed or inactive has been opened again, but only to a limited or incomplete extent.
-
C.
reopenedSection
Indicates that a previously closed or inactive section has been opened again and returned to active or accessible status.
-
D.
reopenedForNavigation
Indicates that something previously closed to traffic or passage has been opened again for navigational use.
-
E.
reopenedAfterReconstruction
Indicates that a place or facility resumed operations after undergoing reconstruction or major rebuilding work.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:19 p.m.