Triple
T8524655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotuma |
E201780
|
entity |
| Predicate | integratedIntoFiji |
P15157
|
FINISHED |
| Object | 1881 |
—
|
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: 1881 | Statement: [Rotuma, integratedIntoFiji, 1881]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoFiji Context triple: [Rotuma, integratedIntoFiji, 1881]
-
A.
integratedIn
chosen
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
B.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
C.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
D.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
E.
isImplementationOf
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe644c4648190a14dcaeaa90d72c7 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.