Triple
T24214545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unaaha |
E600649
|
entity |
| Predicate | belongsToRegency |
P56414
|
FINISHED |
| Object | Konawe |
—
|
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: Konawe | Statement: [Unaaha, belongsToRegency, Konawe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRegency Context triple: [Unaaha, belongsToRegency, Konawe]
-
A.
coregencyOrRegencyFor
Indicates that one entity serves as a regent or co-ruler governing on behalf of another entity, typically during the latter’s minority, incapacity, or absence.
-
B.
isRuralDistrictOf
chosen
Indicates that one administrative area is a rural district that belongs to or is governed as part of another, typically larger, administrative unit.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
belongsToTerritorialCollectivity
Indicates that one entity is administratively or jurisdictionally part of, or under the authority of, a specific territorial collectivity.
-
E.
belongsToMetropolitanRegion
Indicates that one geographic or administrative area is part of, or included within, a larger metropolitan region.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820679a881909483c2d49f16508a |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:57 p.m.