Triple
T33216153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transmission Gully Motorway |
E850295
|
entity |
| Predicate | openingDelayedFrom |
P152233
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Transmission Gully Motorway, openingDelayedFrom, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDelayedFrom Context triple: [Transmission Gully Motorway, openingDelayedFrom, 2020]
-
A.
delayedFrom
chosen
Indicates that something is postponed or starts later than originally scheduled due to a cause or source associated with the referenced entity.
-
B.
openedFrom
Indicates that one entity was initiated, accessed, or launched as a result of an action performed within another entity.
-
C.
openingDynamic
Indicates that one entity initiates or begins another entity or process in a way that can change or vary over time or context.
-
D.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
E.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:30 a.m.