Triple
T10085238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayley Atwell |
E215202
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Atwell |
E678608
|
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: Atwell | Statement: [Hayley Atwell, familyName, Atwell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atwell Context triple: [Hayley Atwell, familyName, Atwell]
-
A.
Atwell
chosen
Atwell is an English-language surname borne by various notable individuals across fields such as entertainment, sports, and public life.
-
B.
Aylward
Aylward is a given name notably borne by the 19th-century Irish zoologist and politician Nicholas Aylward Vigors.
-
C.
Stowell
Stowell is an English surname notably borne by Baroness Stowell of Beeston, a British Conservative politician and life peer.
-
D.
Aylott
Aylott is a surname most notably associated with the British publishing firm Aylott and Jones.
-
E.
Hartwell
Hartwell is a residential suburb in Melbourne, Victoria, known for its leafy streets, family-friendly atmosphere, and access to local train and tram services.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04609748190987a9364a387fa61 |
completed | April 2, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b68188c48190ac783cdfc072c502 |
completed | April 5, 2026, 7:22 p.m. |
Created at: March 30, 2026, 9 p.m.