Triple
T26626597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atoni people |
E668365
|
entity |
| Predicate | mainRegency |
P153545
|
FINISHED |
| Object | Kupang Regency |
—
|
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: Kupang Regency | Statement: [Atoni people, mainRegency, Kupang Regency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRegency Context triple: [Atoni people, mainRegency, Kupang Regency]
-
A.
hasRegency
Indicates that one entity exercises regency authority or governing power on behalf of another, typically during the latter’s minority, incapacity, or absence.
-
B.
isLocatedInRegency
chosen
Indicates that one entity (typically a place or facility) is situated within the administrative area of a specific regency.
-
C.
governingRegency
Indicates that one entity is serving as the regent, exercising governing authority on behalf of another (typically a ruler or state).
-
D.
regencyCapital
Indicates that a location serves as the administrative capital or seat of government for a regency-level jurisdiction.
-
E.
hasRegencyType
Indicates that an entity is associated with a specific type or form of regency (i.e., a particular kind of regent rule or regent arrangement).
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 2:23 a.m.