Triple
T26803680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woden Valley |
E671166
|
entity |
| Predicate | hasCivicFunctions |
P17162
|
FINISHED |
| Object | Woden Town Centre |
—
|
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: Woden Town Centre | Statement: [Woden Valley, hasCivicFunctions, Woden Town Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivicFunctions Context triple: [Woden Valley, hasCivicFunctions, Woden Town Centre]
-
A.
hasCivicFunction
chosen
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
B.
hasCivicElements
Indicates that something includes or involves aspects related to civic life, responsibilities, or public affairs.
-
C.
hasCivicOrganization
Indicates that an entity is associated with, supported by, or contains a civic organization, such as a community, volunteer, or public-interest group.
-
D.
hasCivicLeader
Indicates that an entity serves as the civic leader (such as a mayor or equivalent public official) of another entity, typically a city or municipality.
-
E.
hasCommitteeFunction
Indicates that a committee is assigned or performs a specific function, role, or responsibility.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 4:24 a.m.