Triple
T25417748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 15 |
E636886
|
entity |
| Predicate | isUrbanRoadIn |
P52196
|
FINISHED |
| Object | Brisbane metropolitan area |
—
|
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: Brisbane metropolitan area | Statement: [State Route 15, isUrbanRoadIn, Brisbane metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanRoadIn Context triple: [State Route 15, isUrbanRoadIn, Brisbane metropolitan area]
-
A.
isUrbanStreet
Indicates that a given street is located within an urban area or city environment rather than a rural or suburban setting.
-
B.
isUrbanRoute
chosen
Indicates that a route is located within, passes through, or primarily serves an urban or metropolitan area.
-
C.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
D.
isUrbanFreeway
Indicates that a roadway segment functions as a high-capacity, limited-access freeway located within an urban area.
-
E.
isUrbanNode
Indicates that a location or entity functions as an urban center or node within a city or metropolitan network.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b013596c81909af7acebfc72bfc6 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:55 p.m.