Triple
T13605300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Armistead Tyler |
E325045
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Armistead |
E463964
|
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: Armistead | Statement: [Mary Armistead Tyler, familyName, Armistead]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Armistead Context triple: [Mary Armistead Tyler, familyName, Armistead]
-
A.
Armistead
chosen
Armistead is a surname most notably associated with Lewis Armistead, a Confederate general during the American Civil War.
-
B.
Bayard
Bayard is a masculine given name most notably associated with civil rights leader Bayard Rustin.
-
C.
Bayard
Bayard is a small rural city in western Nebraska known for its agricultural community and proximity to landmarks like Chimney Rock.
-
D.
Bayard
Bayard is a small town in Grant County, West Virginia, known historically as a coal and timber community in the Appalachian region.
-
E.
Bayard
Bayard is a small city located in Guthrie County in the state of Iowa, United States.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07e442c819086a8cbb967c03ad3 |
completed | April 12, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f93ec588190993baec788d22670 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:50 p.m.