Triple
T13481057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Mercer |
E318371
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mercer |
E216363
|
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: Mercer | Statement: [Ray Mercer, familyName, Mercer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mercer Context triple: [Ray Mercer, familyName, Mercer]
-
A.
Mercer
chosen
Mercer is a surname of Scottish and English origin borne by various notable individuals, including the American Revolutionary War general Hugh Mercer.
-
B.
Mercer
Mercer is a global consulting firm specializing in human resources, health, retirement, and investment solutions.
-
C.
Wilmore
Wilmore is a small city in central Kentucky known for its strong Christian academic community and as the home of Asbury University and Asbury Theological Seminary.
-
D.
Wilmore
Wilmore is an English-language surname borne by various notable individuals across fields such as entertainment, sports, and public service.
-
E.
Aiken
Aiken is a variant spelling of the surname Aitken, which is of Scottish origin.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf36c6b08190ba99400600e0b662 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74635145c8190a42199fe4ed8c2a5 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:42 p.m.