Triple
T1154562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adriatic Sea |
E23753
|
entity |
| Predicate | hasManyIslands |
P970
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Adriatic Sea, hasManyIslands, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManyIslands Context triple: [Adriatic Sea, hasManyIslands, yes]
-
A.
hasIsland
chosen
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
B.
hasSisterIsland
Indicates that one island is considered a sister island of another, typically implying a special paired or closely associated relationship between them.
-
C.
hasIslandArc
Indicates that one geographic or geological entity possesses or is associated with an island arc feature.
-
D.
locatedInArchipelago
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
E.
meetsInIsland
Indicates that two or more entities meet with each other at a location that is 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc8fbb548190865b1bf019f2bde4 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.