Triple
T29778454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrabble (US game show) |
E755444
|
entity |
| Predicate | usesGameElement |
P3097
|
FINISHED |
| Object | letter tiles |
—
|
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: letter tiles | Statement: [Scrabble (US game show), usesGameElement, letter tiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGameElement Context triple: [Scrabble (US game show), usesGameElement, letter tiles]
-
A.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
B.
gameElement
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
C.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
developerOfGameUsed
Indicates that an entity is the developer of a game that is (or was) used or played in a given context.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f674a46ba481908229b8389887074d |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 8:48 p.m.