Triple
T13787159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cluedo (TV series) |
E331290
|
entity |
| Predicate | usesElementsFrom |
P64959
|
FINISHED |
| Object | board game mechanics |
—
|
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: board game mechanics | Statement: [Cluedo (TV series), usesElementsFrom, board game mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElementsFrom Context triple: [Cluedo (TV series), usesElementsFrom, board game mechanics]
-
A.
usesElementsOf
chosen
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
B.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
C.
incorporatesElementsFrom
Indicates that one entity includes or integrates components, features, or aspects derived from another entity.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.