Triple
T27912362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapaʻata |
E705965
|
entity |
| Predicate | hasRelativeLocationOnIsland |
P16601
|
FINISHED |
| Object | northern part of Niuafoʻou Island |
—
|
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: northern part of Niuafoʻou Island | Statement: [Sapaʻata, hasRelativeLocationOnIsland, northern part of Niuafoʻou Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeLocationOnIsland Context triple: [Sapaʻata, hasRelativeLocationOnIsland, northern part of Niuafoʻou Island]
-
A.
relativeLocationOnIsland
chosen
Indicates a spatial relationship where one entity’s position is described relative to another entity specifically in the context of being on an island.
-
B.
isInIsland
Indicates that one entity is located within the geographic boundaries of an island.
-
C.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
D.
isOnSideOfIsland
Indicates that one entity is located on a particular side or shore of an island relative to some reference or division.
-
E.
locatedInRegionOfIsland
Indicates that an entity is situated within a specific region that is part of an island.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 27, 2026, 6:51 p.m.