Triple
T10426478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Lusser |
E245801
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lusser |
E245801
|
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: Lusser | Statement: [Robert Lusser, familyName, Lusser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lusser Context triple: [Robert Lusser, familyName, Lusser]
-
A.
Lusser
chosen
Lusser is a German surname most notably associated with engineer Robert Lusser, known for his contributions to aeronautics and reliability engineering.
-
B.
Loerzer
Loerzer is the surname of Bruno Loerzer, a notable German First World War flying ace and later Luftwaffe general.
-
C.
Lardé
Lardé is the surname of Alicia Esther Lardé, a Salvadoran-born physicist and the first wife of mathematician John Nash.
-
D.
Gsell
Gsell is a surname of Germanic origin borne by various notable individuals, including artists, scholars, and public figures.
-
E.
Lebrun
Lebrun is a French surname borne by various notable figures in politics, arts, and other fields.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea498ab08190b451c0b257c0711b |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fc2b50b48190b1d5b29d19a240c2 |
completed | April 9, 2026, 7:21 p.m. |
Created at: April 6, 2026, 12:12 p.m.