Triple
T6689413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo Amery |
E152585
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Amery |
E75162
|
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: Amery | Statement: [Leo Amery, familyName, Amery]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amery Context triple: [Leo Amery, familyName, Amery]
-
A.
Amery
chosen
Amery is an English surname most notably associated with a British political family, including Conservative politician Julian Amery.
-
B.
Amer
Amer is a common Arabic surname borne by various notable individuals across the Middle East and North Africa.
-
C.
Ameria
Ameria is an ancient Umbrian town in central Italy, known today as Amelia, with significant archaeological and historical remains from pre-Roman and Roman times.
-
D.
Beni-Amer
The Beni-Amer are a pastoralist ethnic group of mixed Beja and Tigre heritage living primarily in eastern Sudan and western Eritrea.
-
E.
Amri
Amri is an archaeological site in present-day Pakistan associated with the early phases of the Indus Valley Civilization.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6b15149408190ac679d037d87cba7 |
completed | March 27, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7b519148190a810d0eee7cda734 |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2:04 p.m.