Triple
T23109118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cres |
E576265
|
entity |
| Predicate | hasFerryConnectionTo |
P1831
|
FINISHED |
| Object | Krk |
—
|
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: Krk | Statement: [Cres, hasFerryConnectionTo, Krk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krk Context triple: [Cres, hasFerryConnectionTo, Krk]
-
A.
Krk
chosen
Krk is a large Adriatic Sea island in the northern part of Croatia, known for its historic towns, beaches, and popular tourist resorts.
-
B.
Krasici
Krasici is a small coastal village in Montenegro situated along the shores of the Bay of Kotor, known for its seaside tourism and scenic Adriatic views.
-
C.
Krndija
Krndija is a low mountain range in eastern Croatia known for its forested landscapes and proximity to the town of Požega.
-
D.
Krnjak
Krnjak is a small municipality and village located in central Croatia, known for its rural character and mixed ethnic population.
-
E.
Kornica
Kornica is a village located within the administrative district of Gmina Końskie in south-central Poland.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0d3d4881908e32837b3fbbb406 |
completed | April 29, 2026, 4:50 a.m. |
Created at: April 17, 2026, 3:58 p.m.