Triple
T35543284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Checkers |
E1027121
|
entity |
| Predicate | hasMisleadingName |
P153365
|
FINISHED |
| Object | not of Chinese origin |
—
|
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: not of Chinese origin | Statement: [Chinese Checkers, hasMisleadingName, not of Chinese origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMisleadingName Context triple: [Chinese Checkers, hasMisleadingName, not of Chinese origin]
-
A.
nameIsMisnomerFor
chosen
Indicates that the given name inaccurately or misleadingly describes the entity it refers to.
-
B.
misrepresentedAs
Indicates that one entity is falsely or inaccurately presented, portrayed, or described as another entity or in another way.
-
C.
notRealNameOf
Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that entity).
-
D.
misrepresentedIn
Indicates that something is inaccurately or falsely portrayed within a particular source, context, or representation.
-
E.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:04 p.m.