Triple
T34025406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granite Belt |
E872494
|
entity |
| Predicate | regionCentre |
P128866
|
FINISHED |
| Object | Stanthorpe |
—
|
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: Stanthorpe | Statement: [Granite Belt, regionCentre, Stanthorpe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCentre Context triple: [Granite Belt, regionCentre, Stanthorpe]
-
A.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
-
B.
hasRegionCenter
chosen
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
C.
servesAsCentreFor
Indicates that one entity functions as the main hub, focal point, or primary location for the activities, services, or operations of another entity.
-
D.
metropolitanRegionCenter
Indicates that one location functions as the central or primary hub of a specified metropolitan region.
-
E.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 1, 2026, 1:51 a.m.