Triple
T7072063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Emery |
E164721
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Emery |
E446971
|
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: Emery | Statement: [John Emery, hasFamilyName, Emery]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emery Context triple: [John Emery, hasFamilyName, Emery]
-
A.
Emery
chosen
Emery is a surname of English origin borne by various notable individuals, including Sarah Jane Emery.
-
B.
Kimsey
Kimsey is a surname most notably associated with Jim Kimsey, the co-founder and first CEO of America Online (AOL).
-
C.
Larue
Larue is a Vietnamese beer brand produced by Asia Pacific Breweries, known for its pale lager popular in central Vietnam.
-
D.
Finklea
Finklea is the birth surname of American actress and dancer Cyd Charisse, known for her roles in classic Hollywood musicals.
-
E.
Tilghman
Tilghman is a masculine given name of English origin that has been borne by various notable American figures, including politicians and military officers.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4c9cdbc8190b91cd3b4eef58eb6 |
completed | March 27, 2026, 8:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7945fdafc81909c265373627af4e8 |
completed | March 28, 2026, 8:42 a.m. |
Created at: March 27, 2026, 2:39 p.m.