Triple
T33933021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnmoney |
E869949
|
entity |
| Predicate | OSMRelationType |
P177932
|
FINISHED |
| Object | suburb |
—
|
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: suburb | Statement: [Carnmoney, OSMRelationType, suburb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OSMRelationType Context triple: [Carnmoney, OSMRelationType, suburb]
-
A.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
B.
cityInfrastructureRelation
Indicates a relationship between a city and elements of its infrastructure, such as facilities, networks, or services that support its functioning.
-
C.
roadDistanceRelation
Indicates a relationship specifying the distance between two locations as measured along a road or road network.
-
D.
typeOfMunicipalRelationship
Indicates a formal type or category of administrative or cooperative relationship that exists between municipalities.
-
E.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.