Triple
T34454301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Puke |
E884460
|
entity |
| Predicate | adminDivisionLevel2 |
P53398
|
FINISHED |
| Object | Futuna Island |
—
|
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: Futuna Island | Statement: [Mont Puke, adminDivisionLevel2, Futuna Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminDivisionLevel2 Context triple: [Mont Puke, adminDivisionLevel2, Futuna Island]
-
A.
hasSecondLevelAdministrativeTerritory
chosen
Indicates that an entity possesses or includes a second-level administrative division within its territorial or organizational hierarchy.
-
B.
lowerLevelSubdivision
Indicates that one administrative or organizational unit is a smaller, subordinate subdivision within another, higher-level unit.
-
C.
regionDivision
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
-
D.
higherAdministrativeDivision
Indicates that one administrative unit is hierarchically above and has jurisdiction over another within an administrative structure.
-
E.
collectionSubdivision
Indicates that one collection is a constituent part, section, or subdivision of a larger collection.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 1, 2026, 2 a.m.