Triple
T22599699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aimee Mullins |
E574779
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mullins |
—
|
NE NERFINISHED |
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: Mullins | Statement: [Aimee Mullins, familyName, Mullins]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mullins Context triple: [Aimee Mullins, familyName, Mullins]
-
A.
Mullins
chosen
Mullins is an English-language surname of Irish and Norman origin borne by various notable individuals across history.
-
B.
Mullett
Mullett is a surname most notably associated with Alfred B. Mullett, a 19th-century American architect known for designing prominent federal buildings.
-
C.
Mullane
Mullane is a surname of Irish origin, considered a variant of the name Mullen.
-
D.
Moloney
Moloney is an Irish-origin surname borne by various notable individuals in fields such as entertainment, sports, and politics.
-
E.
Mullally
Mullally is a surname of Irish origin borne by various notable individuals in fields such as entertainment, sports, and public service.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626b5f5481909a104088d1c96720 |
completed | April 29, 2026, 1:44 a.m. |
Created at: April 17, 2026, 2:50 p.m.