Triple
T12122923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Randonnée network |
E288737
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | GR 11 |
E288739
|
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: GR 11 | Statement: [Grande Randonnée network, hasPart, GR 11]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GR 11 Context triple: [Grande Randonnée network, hasPart, GR 11]
-
A.
GR 11
chosen
GR 11 is a long-distance hiking trail that traverses the Spanish side of the Pyrenees from the Atlantic Ocean to the Mediterranean Sea.
-
B.
GR 10
GR 10 is a long-distance hiking trail that traverses the French side of the Pyrenees from the Atlantic Ocean to the Mediterranean Sea.
-
C.
GR10
GR10 is a renowned long-distance hiking trail that traverses the French Pyrenees from the Atlantic Ocean to the Mediterranean Sea.
-
D.
GR
GR is the standard abbreviation for Georgian Railway, the national rail transport company of Georgia.
-
E.
GR
GR is the official two-letter abbreviation used to designate the Swiss canton of Graubünden.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91578fd88819099adf55c93d549fc |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f686d6c08190b1f1ca2d5a51f5df |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:49 p.m.