Triple
T1932401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldridge |
E40974
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Eldridge |
E164159
|
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: Eldridge | Statement: [Aldridge, hasVariant, Eldridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eldridge Context triple: [Aldridge, hasVariant, Eldridge]
-
A.
Eldridge
chosen
Eldridge is an English-language surname of Old English origin, borne by various notable individuals across fields such as politics, the arts, and sports.
-
B.
Leland
Leland is a masculine given name of English origin, historically associated with figures such as American industrialist and Stanford University founder Leland Stanford.
-
C.
Dedridge
Dedridge is a residential neighbourhood within the new town of Livingston in West Lothian, Scotland.
-
D.
Willard
Willard is a masculine given name of Old English origin meaning "resolute" or "strong-willed."
-
E.
Riggs
Riggs is a surname most notably associated with American playwright Lynn Riggs, whose work inspired the musical "Oklahoma!".
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb297ec2c819092ad62d72005223d |
completed | March 7, 2026, 5:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3f16d0c8190967862b68e6cc373 |
completed | March 8, 2026, 10:10 p.m. |
Created at: March 4, 2026, 7:35 p.m.