Triple
T14592145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan City Council area |
E342470
|
entity |
| Predicate | governsCommunityType |
P3292
|
FINISHED |
| Object | residential communities |
—
|
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: residential communities | Statement: [Logan City Council area, governsCommunityType, residential communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsCommunityType Context triple: [Logan City Council area, governsCommunityType, residential communities]
-
A.
governedCommunity
Indicates that one entity exercises governing authority or administrative control over a community or group of people.
-
B.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
C.
governedCategory
Indicates that one category is subject to the control, regulation, or authority of another entity or governing framework.
-
D.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
E.
hasLocalGovernanceType
Indicates the specific form or system of local governance that applies to an 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4249af08190962009741d1f7d41 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.