Triple
T25252235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cigogne Island |
E632771
|
entity |
| Predicate | archipelagoMemberOf |
P7765
|
FINISHED |
| Object | Glénan archipelago |
—
|
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: Glénan archipelago | Statement: [Cigogne Island, archipelagoMemberOf, Glénan archipelago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archipelagoMemberOf Context triple: [Cigogne Island, archipelagoMemberOf, Glénan archipelago]
-
A.
archipelagoType
Indicates the specific kind or classification of an archipelago based on its characteristics or formation.
-
B.
includesArchipelago
Indicates that one geographic entity contains or encompasses an archipelago within its area or jurisdiction.
-
C.
islandGroupOf
Indicates that one entity is an island that belongs to, or is a member of, a specified group or chain of islands.
-
D.
locatedInArchipelago
chosen
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
E.
archipelagoStatus
Indicates that an entity has the status or classification of being an archipelago, typically denoting a group or chain of islands considered as a single geographic or administrative unit.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:11 p.m.