Triple
T28904805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miniplenty |
E733042
|
entity |
| Predicate | contradictoryName |
P153365
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Miniplenty, contradictoryName, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contradictoryName Context triple: [Miniplenty, contradictoryName, yes]
-
A.
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.
-
B.
paradoxName
Indicates that an entity is the name or label of a paradox associated with another entity.
-
C.
nameIsMisnomerFor
chosen
Indicates that the given name inaccurately or misleadingly describes the entity it refers to.
-
D.
namesakeConflict
Indicates a situation where two or more entities share the same or very similar name, causing ambiguity or confusion in identifying or distinguishing them.
-
E.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 8:06 a.m.