Triple
T13217991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierre Lazareff |
E314671
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lazareff |
E771430
|
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: Lazareff | Statement: [Pierre Lazareff, familyName, Lazareff]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lazareff Context triple: [Pierre Lazareff, familyName, Lazareff]
-
A.
Lazzara
Lazzara is the birth surname of acclaimed American actress and singer Bernadette Peters.
-
B.
Lusser
Lusser is a German surname most notably associated with engineer Robert Lusser, known for his contributions to aeronautics and reliability engineering.
-
C.
Gordon-Lazareff
chosen
Gordon-Lazareff is the surname of Hélène Gordon-Lazareff, a notable French journalist and founder of the women’s magazine Elle.
-
D.
Gazelli
Gazelli is an Italian noble family name associated with the aristocratic lineage of Luisa Gazelli dei Conti di Rossana.
-
E.
Loerzer
Loerzer is the surname of Bruno Loerzer, a notable German First World War flying ace and later Luftwaffe general.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf392e08190949ee4d194566395 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff2085f88190be8cfc309d21f9cb |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:18 p.m.