Triple
T11736165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adour |
E279030
|
entity |
| Predicate | locatedInDepartment |
P40
|
FINISHED |
| Object | Gers |
E752250
|
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: Gers | Statement: [Adour, locatedInDepartment, Gers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gers Context triple: [Adour, locatedInDepartment, Gers]
-
A.
Gers
Gers is a river in southwestern France that flows through the historical region of Gascony before joining the Garonne.
-
B.
Gers
chosen
Gers is a rural department in southwestern France known for its rolling countryside, traditional Gascon culture, and production of Armagnac brandy and foie gras.
-
C.
The Gers
The Gers is a popular nickname for Rangers F.C., one of Scotland’s most successful and widely supported football clubs.
-
D.
Gersprenz
Gersprenz is a river in the German state of Hesse that flows through the Odenwald region before joining the Main River system.
-
E.
Gsell
Gsell is a surname of Germanic origin borne by various notable individuals, including artists, scholars, and public figures.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4edced48190b7a59dd45921828e |
completed | April 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f019b318188190bfb7effcf42974d2 |
completed | April 28, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:41 p.m.