Triple
T26509289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth Road Bridge steelwork (contractor) |
E669633
|
entity |
| Predicate | openingRelatedDate |
P121857
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [Forth Road Bridge steelwork (contractor), openingRelatedDate, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingRelatedDate Context triple: [Forth Road Bridge steelwork (contractor), openingRelatedDate, 1964]
-
A.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
B.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
-
C.
openingDateLineC
chosen
Indicates the calendar date on which entity C is opened, initiated, or begins operation.
-
D.
openingRelatedTo
Indicates a relationship where one entity’s opening (such as a beginning, introduction, or initial part) is connected or relevant to another entity.
-
E.
openingPressDaysEnd
Indicates the point in time when the designated opening press days period concludes.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:19 a.m.