Triple
T16140281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GR 20 |
E391634
|
entity |
| Predicate | endPoint |
P390
|
FINISHED |
| Object | Conca |
E391637
|
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: Conca | Statement: [GR 20, endPoint, Conca]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Conca Context triple: [GR 20, endPoint, Conca]
-
A.
Conca
chosen
Conca is a small commune in southern Corsica, France, known as a gateway village for hikers on the famous GR20 long-distance trail.
-
B.
Quarracino
Quarracino is an Italian-origin surname most notably associated with Argentine Cardinal Antonio Quarracino.
-
C.
Casarico
Casarico is a locality or hamlet that forms part of the municipality of Moltrasio in the Lombardy region of northern Italy.
-
D.
Nigoglia
Nigoglia is the short river in northern Italy that uniquely flows northward out of Lake Orta toward the Strona and ultimately the Toce River.
-
E.
Vicovaro
Vicovaro is a historic Italian locality in Lazio that was once a feudal possession of the powerful Orsini noble family.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a07b7908190b4e1ec57f60a9274 |
completed | April 17, 2026, 11:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff2b75988819094baaff8f53f48ce |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 5:01 a.m.