Triple
T17272715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zawe Ashton |
E419304
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ashton |
E236180
|
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: Ashton | Statement: [Zawe Ashton, familyName, Ashton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashton Context triple: [Zawe Ashton, familyName, Ashton]
-
A.
Ashton
chosen
Ashton is a masculine given name of English origin that has become well known through figures such as actor and entrepreneur Ashton Kutcher.
-
B.
Ashton
Ashton is a small village in the town of Cumberland in Providence County, Rhode Island, known for its historic mill district along the Blackstone River.
-
C.
Ashton
Ashton is a small village in Cornwall, England, known for its rural character and location within the civil parish of Breage.
-
D.
Ashton
Ashton is a small coastal town on Union Island in Saint Vincent and the Grenadines, known as one of the island’s main settlements.
-
E.
Ashton
Ashton is a small city located in Osceola County in the northwestern part of the U.S. state of Iowa.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4b023c8190b92df4015c14c3a8 |
completed | April 19, 2026, 1:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01794d605481908b5e430c3142c203 |
completed | May 11, 2026, 6:38 a.m. |
Created at: April 10, 2026, 5:40 a.m.