Triple
T12159476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alvan Adams |
E289666
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Alvan |
E876044
|
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: Alvan | Statement: [Alvan Adams, givenName, Alvan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alvan Context triple: [Alvan Adams, givenName, Alvan]
-
A.
Alvan
chosen
Alvan is a masculine given name of English origin, notably borne by figures such as U.S. Army officer Alvan C. Gillem.
-
B.
Everard
Everard is a masculine given name of Old English origin, historically meaning “brave boar” or “strong as a wild boar.”
-
C.
Allan Case
Allan Case is a notable individual distinguished enough to be recognized as a prominent bearer of the surname Case.
-
D.
Ottis
Ottis is a masculine given name most notably borne by former NFL running back Ottis Anderson.
-
E.
John Henry Kagi
John Henry Kagi was an abolitionist and close associate of John Brown who served as a key lieutenant and strategist in the lead-up to the 1859 Harpers Ferry raid.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915c277e481908351bf4e664dda42 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f69e8498819080d571e6fb4edfde |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:50 p.m.