Triple
T26190682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koster Islands |
E654953
|
entity |
| Predicate | hasLargestIslands |
P127381
|
FINISHED |
| Object | North Koster |
—
|
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: North Koster | Statement: [Koster Islands, hasLargestIslands, North Koster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLargestIslands Context triple: [Koster Islands, hasLargestIslands, North Koster]
-
A.
isLargestIslandIn
chosen
Indicates that one island is the largest (by area) among all islands within a specified geographic or political region.
-
B.
hasNumberOfMajorIslands
Indicates the quantitative relationship specifying how many major islands are associated with a given entity.
-
C.
hasNumberOfInhabitedIslands
Indicates the relationship that specifies how many islands within a given area or jurisdiction are inhabited.
-
D.
hasMajorIslandToSouth
Indicates that the subject entity has a major island located geographically to its south.
-
E.
hasSisterIsland
Indicates that one island is considered a sister island of another, typically implying a special paired or closely associated relationship between them.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 26, 2026, 8:44 p.m.