Triple
T22933630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tukang Besi people |
E569512
|
entity |
| Predicate | regionFormerName |
P28982
|
FINISHED |
| Object | Tukang Besi Islands |
—
|
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: Tukang Besi Islands | Statement: [Tukang Besi people, regionFormerName, Tukang Besi Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionFormerName Context triple: [Tukang Besi people, regionFormerName, Tukang Besi Islands]
-
A.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
B.
regionHistoricalName
chosen
Indicates that a region has been known by a particular historical name during some past period.
-
C.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
D.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
-
E.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181337ff881909d90cf3f5bae7516 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.