Triple
T9117178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan Mowbray |
E218749
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Allen |
E105455
|
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: Allen | Statement: [Alan Mowbray, familyName, Allen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Allen Context triple: [Alan Mowbray, familyName, Allen]
-
A.
Allen
chosen
Allen is a common English-language surname borne by numerous notable individuals across politics, sports, entertainment, and other fields.
-
B.
Allen
Allen is a suburban city in Collin County, Texas, known for its rapid growth, family-friendly communities, and location within the Dallas–Fort Worth metropolitan area.
-
C.
Allen
Allen is a city in Argentina’s Alto Valle region, known primarily for its fruit production and agriculture-based economy.
-
D.
Allen
Allen was the French-made leather football used as the official match ball of the 1938 FIFA World Cup.
-
E.
Anderson
Anderson is a city in South Carolina known as a regional hub in the Upstate area and part of the Greenville-Anderson-Mauldin metropolitan region.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a5e2ac8190b602ef0c77deb2fa |
completed | April 1, 2026, 5:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0307299ec8190acade4f388642e23 |
completed | April 3, 2026, 9:26 p.m. |
Created at: March 30, 2026, 7:17 p.m.