Triple
T36508172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otago goldfields |
E899824
|
entity |
| Predicate | infrastructureDeveloped |
P98788
|
FINISHED |
| Object | roads |
—
|
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: roads | Statement: [Otago goldfields, infrastructureDeveloped, roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureDeveloped Context triple: [Otago goldfields, infrastructureDeveloped, roads]
-
A.
infrastructureLevel
Indicates the degree or quality of infrastructure present or provided in relation to an entity or location.
-
B.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
infrastructureArrangements
Indicates the organizational or contractual setup governing how infrastructure components are planned, provided, interconnected, or managed in relation to one another.
-
D.
typicalInfrastructure
chosen
Indicates that something is part of the standard or commonly expected infrastructure associated with a given context or entity.
-
E.
hasInfrastructureAlong
Indicates that infrastructure is present or extends along the length or course of another entity (such as a route, boundary, or geographic feature).
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.