Triple
T33216184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transmission Gully Motorway |
E850295
|
entity |
| Predicate | hasMedianBarrier |
P198066
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Transmission Gully Motorway, hasMedianBarrier, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedianBarrier Context triple: [Transmission Gully Motorway, hasMedianBarrier, yes]
-
A.
hasMedianUse
Indicates that something is associated with a typical or middle level of use within a given range or distribution of usage.
-
B.
isBarrierTo
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
C.
medianEquals
Indicates that the median value of a given set or sequence is equal to a specified value.
-
D.
hasPitchBarrier
Indicates that there is a physical or structural barrier affecting or limiting the pitch (height or angle) between related entities.
-
E.
runsInMedianOf
Indicates that an entity operates or occurs within the median (middle) portion of another entity, such as a roadway or distribution range.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
| PDg | Predicate description generation | batch_69fec5c3f8248190b835a8e4eba470c4 |
completed | May 9, 2026, 5:27 a.m. |
Created at: May 1, 2026, 1:30 a.m.