Triple
T17049076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adriatic islands |
E413646
|
entity |
| Predicate | hasNotableIsland |
P970
|
FINISHED |
| Object | Vis |
E442093
|
NE 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: Vis | Statement: [Adriatic islands, hasNotableIsland, Vis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vis Context triple: [Adriatic islands, hasNotableIsland, Vis]
-
A.
Vis
chosen
Vis is a Croatian island in the Adriatic Sea known for its unspoiled nature, historic towns, and former role as a strategic military base.
-
B.
Vis
Vis is a river in southern France known for carving the dramatic Cirque de Navacelles canyon through the limestone plateaus of the Cévennes region.
-
C.
VIS
VIS is the IATA airport code for Visalia Municipal Airport in Visalia, California, United States.
-
D.
VIS
VIS is a large-scale European Union database system used to store and exchange visa application and related biometric data among member states’ authorities.
-
E.
Vin
Vin is a common shortened form of the given name Vincent, often used as an informal or familiar nickname.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa092f08190a9e37404a9de662c |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012341b8e88190a2bee865be5ca1c1 |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.