Triple
T7614419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurrajong |
E172324
|
entity |
| Predicate | hasGovernmentRegionType |
P62377
|
FINISHED |
| Object | urban electorate |
—
|
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: urban electorate | Statement: [Kurrajong, hasGovernmentRegionType, urban electorate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentRegionType Context triple: [Kurrajong, hasGovernmentRegionType, urban electorate]
-
A.
hasGovernmentTypeCountry
Indicates that a country possesses or is characterized by a particular form or type of government.
-
B.
politicalRegionType
chosen
Indicates the classification of a political region according to its governmental or administrative type (e.g., state, province, municipality).
-
C.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
D.
hasRegionalGovernor
Indicates that a region is administered or overseen by a specific governor responsible for its governance.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa4392e881908ed1ab3f64b41600 |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.