Triple
T17524871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iTaukei Fijians |
E426768
|
entity |
| Predicate | formerOfficialTerm |
P12531
|
FINISHED |
| Object | Fijian |
—
|
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: Fijian | Statement: [iTaukei Fijians, formerOfficialTerm, Fijian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerOfficialTerm Context triple: [iTaukei Fijians, formerOfficialTerm, Fijian]
-
A.
formerOfficialNameOf
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
B.
formerOfficialIn
Indicates that an entity once held an official position or office within another entity but no longer does.
-
C.
formerDesignation
chosen
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
D.
officiallyAdopted
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
-
E.
laterOfficialName
Indicates that an entity was known by one name at an earlier time and was officially renamed to a different name at a later time.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d592a081909bf876d606158b2d |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.