Triple
T13909286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etienne Louw |
E334441
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Etienne |
E278724
|
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: Etienne | Statement: [Etienne Louw, hasGivenName, Etienne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Etienne Context triple: [Etienne Louw, hasGivenName, Etienne]
-
A.
Étienne
chosen
Étienne is the given first name of the French Symbolist poet Stéphane Mallarmé.
-
B.
Estienne
Estienne is the surname of a prominent French family of Renaissance printers and scholars, notably active in Paris and Geneva.
-
C.
Pierre
Pierre is a masculine given name of French origin that has been borne by numerous notable figures in history, arts, and science.
-
D.
Firmin
Firmin is a French given name notably borne by Firmin Didot, a renowned printer, typefounder, and member of the influential Didot family in the history of typography.
-
E.
Eugène
Eugène is a masculine given name of French origin, derived from the Greek "Eugenios," meaning "well-born" or "noble."
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2721ec6c8190888f4a9d004eb8e0 |
completed | April 14, 2026, 11:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd08dfb9881909a20a07e15c15e92 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:16 p.m.