Triple
T34839793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Council of Penola |
E1004308
|
entity |
| Predicate | hadPrimaryTown |
P92693
|
FINISHED |
| Object | Penola, South Australia |
—
|
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: Penola, South Australia | Statement: [District Council of Penola, hadPrimaryTown, Penola, South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPrimaryTown Context triple: [District Council of Penola, hadPrimaryTown, Penola, South Australia]
-
A.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
B.
primaryTown
chosen
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
C.
hadPrimarySettlementPattern
Indicates that an entity exhibited or was characterized by a particular dominant form or arrangement of human settlement.
-
D.
hadCity
Indicates that an entity was formerly associated with or located in a particular city.
-
E.
formerMainSettlement
Indicates that a location was previously the primary or most important settlement of a given area, but no longer holds that status.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.