Triple
T26234951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammond |
E656138
|
entity |
| Predicate | mainPopulationCentre |
P2106
|
FINISHED |
| Object | Murray Bridge |
E168097
|
NE 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: Murray Bridge | Statement: [Hammond, mainPopulationCentre, Murray Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPopulationCentre Context triple: [Hammond, mainPopulationCentre, Murray Bridge]
-
A.
majorPopulationCenter
Indicates that a location functions as a primary hub of population concentration and activity within a region.
-
B.
hasPopulationCenter
chosen
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
C.
hasPopulationCentreFunction
Indicates that an entity serves as a population centre, fulfilling functions related to the concentration, residence, and support of a population.
-
D.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
E.
notablePopulationCenter
Indicates that a location is recognized as a significant or prominent center of population within a given area or context.
- F. None of above.
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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1253567a74819088a36bb887b7d7e7 |
completed | May 24, 2026, 1:24 a.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 9:01 p.m.