Triple
T4301913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paisley Canal Line |
E99856
|
entity |
| Predicate | reopenedToPassengers |
P10067
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Paisley Canal Line, reopenedToPassengers, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedToPassengers Context triple: [Paisley Canal Line, reopenedToPassengers, 1990]
-
A.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
reopenedAsInternationalTerminal
Indicates that a terminal, previously closed or used differently, has been reopened specifically to function as an international terminal.
-
C.
reopeningDate
chosen
Indicates the date on which something that was previously closed is opened again for use or access.
-
D.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
E.
hasPassengerHandling
Indicates that an entity is responsible for or involved in managing the processes and services related to handling passengers.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b66450819089c9ff6ff9f045e5 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.