Triple
T11534692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trois-Ponts |
E273515
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Lorcé |
E916667
|
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: Lorcé | Statement: [Trois-Ponts, hasSubdivision, Lorcé]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lorcé Context triple: [Trois-Ponts, hasSubdivision, Lorcé]
-
A.
Lorcé
chosen
Lorcé is a small village in the municipality of Stoumont in the province of Liège, Belgium.
-
B.
Sully-sur-Loire
Sully-sur-Loire is a historic commune in north-central France known for its medieval château overlooking the Loire River.
-
C.
Langeac
Langeac is a small commune in south-central France, situated in the Haute-Loire department within the Auvergne-Rhône-Alpes region.
-
D.
Serigny
Serigny is a French given name historically associated with the colonial-era figure Serigny Le Moyne.
-
E.
Remigny
Remigny is a small wine-producing village in the Burgundy region of eastern France, situated near the renowned appellation of Santenay.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839b4bb48190b748ec4119f36c11 |
completed | April 10, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6e7fe305c8190bbf981b2c0e63983 |
completed | April 21, 2026, 2:59 a.m. |
Created at: April 8, 2026, 9:37 p.m.