Triple
T23057978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sit |
E574212
|
entity |
| Predicate | hasNearbyIsland |
P970
|
FINISHED |
| Object | Kornat |
—
|
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: Kornat | Statement: [Sit, hasNearbyIsland, Kornat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kornat Context triple: [Sit, hasNearbyIsland, Kornat]
-
A.
Kornat
chosen
Kornat is the largest and most prominent island in Croatia’s Kornati archipelago, known for its rugged coastline and inclusion within Kornati National Park.
-
B.
Kornos
Kornos is a village located on the Greek island of Lemnos in the North Aegean region.
-
C.
Kornos
Kornos is a village in Cyprus known for its traditional pottery and rural character, located in the Larnaca District.
-
D.
Kopaska
Kopaska is the Indonesian Navy’s elite frogman and special operations unit, specializing in underwater demolition, maritime sabotage, and counter-terrorism missions.
-
E.
Karniow
Karniow is the Polish name for the town of Jägerndorf, historically known as Krnov, in the Czech Republic.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18681bec48190a8226b3d89d19b9f |
completed | April 29, 2026, 4:18 a.m. |
Created at: April 17, 2026, 3:55 p.m.