Triple
T29128996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miguel Montoya |
E738316
|
entity |
| Predicate | nameOftenConfusedWith |
P2289
|
FINISHED |
| Object | Inigo Montoya |
—
|
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: Inigo Montoya | Statement: [Miguel Montoya, nameOftenConfusedWith, Inigo Montoya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameOftenConfusedWith Context triple: [Miguel Montoya, nameOftenConfusedWith, Inigo Montoya]
-
A.
oftenConfusedWith
chosen
Indicates that one entity is frequently mistaken for or thought to be another due to similarity or ambiguity.
-
B.
nameIsMisnomerFor
Indicates that the given name inaccurately or misleadingly describes the entity it refers to.
-
C.
nameContrastsWith
Indicates that one name is deliberately chosen or used to highlight a difference or opposition in meaning, style, or identity relative to another name.
-
D.
nameClarification
Indicates that an additional explanation or specification is provided to clarify an entity’s name or how it should be understood.
-
E.
historicallyConfusedWith
Indicates that one entity has been mistaken for or identified as another entity in historical records, interpretations, or traditions.
- F. None of above.
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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6622c2e1c819093b43ecb65f3fa52 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:30 a.m.