Triple
T18474430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siginaka Islands |
E451391
|
entity |
| Predicate | hasIslandGroupType |
P131785
|
FINISHED |
| Object | small islands |
—
|
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: small islands | Statement: [Siginaka Islands, hasIslandGroupType, small islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIslandGroupType Context triple: [Siginaka Islands, hasIslandGroupType, small islands]
-
A.
isInIslandGroup
Indicates that one geographic entity (typically an island) is located within or belongs to a specific island group or archipelago.
-
B.
associatedWithIslandGroup
Indicates that something has a connection or relationship to a particular group of islands, such as belonging to, being part of, or being relevant to that island group.
-
C.
hasIslandGroupOnOneSide
Indicates that one side or boundary of an entity is adjacent or oriented toward a particular island group.
-
D.
hasIsland
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
E.
coversIslandGroup
Indicates that one geographic entity extends over, includes, or encompasses an entire group of islands.
- F. None of above. chosen
Provenance (4 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53062387481909d4503fc963f9913 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:34 a.m.