Triple
T24881765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rural View |
E622729
|
entity |
| Predicate | supportsUrbanCentre |
P84667
|
FINISHED |
| Object | Mackay |
—
|
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: Mackay | Statement: [Rural View, supportsUrbanCentre, Mackay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUrbanCentre Context triple: [Rural View, supportsUrbanCentre, Mackay]
-
A.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
B.
supportsCity
chosen
Indicates that one entity provides assistance, resources, or backing to a city, helping it function, develop, or achieve its goals.
-
C.
supportsCityCluster
Indicates that one entity provides the necessary resources, infrastructure, or services for a specific city cluster to function or develop.
-
D.
significantUrbanArea
Indicates that a location is classified as a major or important urban center within a broader geographic or administrative context.
-
E.
coversUrbanAreas
Indicates that something extends over, includes, or provides coverage for urban or metropolitan areas.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 5:24 a.m.