Triple
T15946914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napoleon III of France |
E386708
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Louis |
E915066
|
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: Louis | Statement: [Napoleon III of France, givenName, Louis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Louis Context triple: [Napoleon III of France, givenName, Louis]
-
A.
Louis
Louis is the friendly, trumpet-playing alligator who dreams of becoming a jazz musician in Disney's animated film "The Princess and the Frog."
-
B.
Louis
Louis is a member of the British royal family, the youngest child of William, Prince of Wales, and Catherine, Princess of Wales.
-
C.
Louis
Louis is the given name of Louis Althusser, a prominent 20th-century French Marxist philosopher known for his structuralist interpretation of Marxism.
-
D.
Louis
chosen
Louis is the given name of Louis III, who served as Grand Duke of Hesse in the 19th century.
-
E.
Louis
Louis was the given name of Louis II, Duke of Bavaria, a medieval German nobleman and regional ruler.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d1a4c08190afc325491ba38870 |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5ba070c8190b6af6cb21bddd7f1 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.