Triple
T26121972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loddon Mallee region |
E658993
|
entity |
| Predicate | planningRegionFor |
P135147
|
FINISHED |
| Object | regional development |
—
|
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: regional development | Statement: [Loddon Mallee region, planningRegionFor, regional development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningRegionFor Context triple: [Loddon Mallee region, planningRegionFor, regional development]
-
A.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
B.
regionTypePlanned
Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
-
C.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
D.
mapRegion
Indicates a relationship where a map or mapping system corresponds to, covers, or is associated with a specific geographic or logical region.
-
E.
planningUnitFor
chosen
Indicates that one entity serves as the planning unit or organizational basis used to plan, manage, or allocate resources for another entity.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 8:09 p.m.