Triple
T35270770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medal of Honor |
E1018659
|
entity |
| Predicate | commonMisnomer |
P153365
|
FINISHED |
| Object | Congressional Medal of Honor |
—
|
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: Congressional Medal of Honor | Statement: [Medal of Honor, commonMisnomer, Congressional Medal of Honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMisnomer Context triple: [Medal of Honor, commonMisnomer, Congressional Medal of Honor]
-
A.
nameIsMisnomerFor
chosen
Indicates that the given name inaccurately or misleadingly describes the entity it refers to.
-
B.
notableMisconception
Indicates that a commonly held but incorrect belief or understanding exists about the subject.
-
C.
misidentifiedAs
Indicates that one entity has been incorrectly recognized, labeled, or understood as another, distinct entity.
-
D.
misconceptionSource
Indicates that one entity is the origin or cause from which a particular misconception arises or is derived.
-
E.
isOftenMisusedBy
Indicates that something is frequently used incorrectly or inappropriately by a particular entity or group.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:02 p.m.