Triple
T17347299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude Lefort |
E421717
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lefort |
E1135132
|
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: Lefort | Statement: [Claude Lefort, familyName, Lefort]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lefort Context triple: [Claude Lefort, familyName, Lefort]
-
A.
Lefort
chosen
Lefort is a surname most notably associated with Franz Lefort, a 17th-century Genevan-born military officer and close advisor to Russian Tsar Peter the Great.
-
B.
Facio
Facio is a surname of Spanish and Italian origin borne by various notable individuals, including figures in politics, the arts, and academia.
-
C.
Latrille
Latrille is a French surname notably borne by Charles Ferdinand Latrille, Comte de Lorencez, a 19th-century French general.
-
D.
Lefortovo
Lefortovo is a Moscow Metro station on the Big Circle Line serving the historic Lefortovo district of Russia’s capital.
-
E.
Fournier
Fournier is a French surname borne by numerous notable figures across fields such as music, sports, politics, and the arts.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2a2ee48190976732e654a40053 |
completed | April 19, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0195546198819085804ec0b5b18040 |
completed | May 11, 2026, 8:37 a.m. |
Created at: April 10, 2026, 5:44 a.m.