Triple
T36854449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coopernook |
E910756
|
entity |
| Predicate | previousHighwayRoute |
P135070
|
FINISHED |
| Object | Old Pacific Highway |
—
|
NE NERFINISHED |
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: Old Pacific Highway | Statement: [Coopernook, previousHighwayRoute, Old Pacific Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHighwayRoute Context triple: [Coopernook, previousHighwayRoute, Old Pacific Highway]
-
A.
successorHighway
Indicates that one highway directly follows or continues from another in a sequence or route.
-
B.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
C.
formerConstituentHighway
chosen
Indicates that a highway was once part of, but is no longer included in, another highway or highway system.
-
D.
followsHighway
Indicates that one entity’s path or route runs along, parallels, or adheres closely to the course of a specified highway.
-
E.
rangeHighwayApprox
Indicates that one entity is approximately within the range or vicinity of a highway associated with another entity.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.