Triple
T14765939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehcad Brooks |
E346994
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Mehcad |
E346994
|
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: Mehcad | Statement: [Mehcad Brooks, givenName, Mehcad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mehcad Context triple: [Mehcad Brooks, givenName, Mehcad]
-
A.
Mehcad
chosen
Mehcad is a masculine given name most notably borne by American actor and former model Mehcad Brooks.
-
B.
Mehmo
Mehmo is a diminutive or affectionate nickname derived from the Turkish given name Mehmet.
-
C.
Manech
Manech is the young French soldier whose mysterious fate during World War I drives the romantic and investigative plot of the novel and film "A Very Long Engagement."
-
D.
MechE
MechE is a common abbreviation for the academic and professional field of mechanical engineering, which focuses on the design, analysis, and manufacture of mechanical systems.
-
E.
Machaon
Machaon is a figure from Greek mythology, renowned as a skilled healer and son of the legendary physician Asclepius.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f576c881909da70627f5897c94 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cf68d94819093567bc630f67b60 |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 10, 2026, 1:30 a.m.