Triple
T22824408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Myers |
E565312
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Myers |
—
|
NE NERFINISHED |
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: Myers | Statement: [Kevin Myers, hasSurname, Myers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Myers Context triple: [Kevin Myers, hasSurname, Myers]
-
A.
Myers
Myers is the middle name of Edwin Myers Shawn, an individual whose full identity incorporates this name as a central component.
-
B.
Myers
chosen
Myers is a surname most notably associated with English film composer Stanley Myers, known for his influential work in cinema music.
-
C.
Meyers
Meyers is a surname shared by various individuals, including members of the wealthy French Bettencourt family.
-
D.
Meyers
Meyers is a small unincorporated community in El Dorado County, California, located near South Lake Tahoe in the Sierra Nevada.
-
E.
Meyer
Meyer is a common German-origin surname borne by numerous notable individuals across fields such as literature, entertainment, sports, and academia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dd34a248190881f2bccdd9aedce |
completed | April 29, 2026, 3:41 a.m. |
Created at: April 17, 2026, 3:34 p.m.