Triple
T16172636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward John Eyre |
E392476
|
entity |
| Predicate | hasPartOfName |
P5298
|
FINISHED |
| Object | Edward |
E5488
|
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: Edward | Statement: [Edward John Eyre, hasPartOfName, Edward]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edward Context triple: [Edward John Eyre, hasPartOfName, Edward]
-
A.
Edward
chosen
Edward is a masculine given name of English origin, historically associated with kings of England and notable figures such as U.S. Senator Edward M. Kennedy.
-
B.
Richard
Richard is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
C.
George
George is the given name of George W. McLaurin, the first African American student admitted to the University of Oklahoma.
-
D.
George
George is the given name of George M. Whitesides, a prominent American chemist known for his influential work in materials science, nanotechnology, and surface chemistry.
-
E.
George
George is the Allied reporting name for the Kawanishi N1K1-J Shiden, a World War II Japanese Navy land-based fighter aircraft.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb88c948190a1d8b5518694ad53 |
completed | April 17, 2026, 11:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000ec9ab2c819098d96dae98f78f50 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:02 a.m.