Triple
T29051939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salisbury, South Australia |
E735281
|
entity |
| Predicate | hasCouncilOffices |
P101558
|
FINISHED |
| Object | City of Salisbury council chambers |
—
|
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: City of Salisbury council chambers | Statement: [Salisbury, South Australia, hasCouncilOffices, City of Salisbury council chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilOffices Context triple: [Salisbury, South Australia, hasCouncilOffices, City of Salisbury council chambers]
-
A.
hasCouncilChambers
chosen
Indicates that an entity possesses or contains designated rooms or facilities used for council meetings or deliberations.
-
B.
hasCouncilStructure
Indicates that an entity is organized or governed according to a specific council-based structure or system.
-
C.
hasBoardOffices
Indicates that an organization maintains official board offices or board-level administrative locations.
-
D.
hasCouncilSeat
Indicates that an entity holds a position or seat on a governing council.
-
E.
hasCouncillors
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: April 28, 2026, 10:08 a.m.