Triple
T8655682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandoy |
E205409
|
entity |
| Predicate | rankInSizeInFaroeIslands |
P29793
|
FINISHED |
| Object | fifth largest 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: fifth largest island | Statement: [Sandoy, rankInSizeInFaroeIslands, fifth largest island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInSizeInFaroeIslands Context triple: [Sandoy, rankInSizeInFaroeIslands, fifth largest island]
-
A.
distance to Tórshavn (kilometers)
Indicates the length, in kilometers, of the shortest travel distance between an entity and the location Tórshavn.
-
B.
rankInSizeInNewZealandIslands
Indicates the ordinal position of an island in New Zealand when ordered by size (e.g., largest, second largest, etc.).
-
C.
rankInNorwayByArea
Indicates the position of an entity in an ordered list of areas within Norway, based on its size relative to others.
-
D.
distanceToLerwickKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the town of Lerwick.
-
E.
relativeSizeInArchipelago
chosen
Indicates the comparative size relationship of an entity relative to other entities within the same archipelago.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4844586081909b687e278496eefa |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.