Triple
T37462266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Awaken the Makers |
E930946
|
entity |
| Predicate | playModeAvailability |
P119199
|
FINISHED |
| Object | Constructed |
—
|
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: Constructed | Statement: [Awaken the Makers, playModeAvailability, Constructed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playModeAvailability Context triple: [Awaken the Makers, playModeAvailability, Constructed]
-
A.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
B.
hasPlayPattern
Indicates a characteristic way or style in which an entity typically plays, behaves, or performs an activity.
-
C.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
D.
playPolicy
Indicates that an entity enforces or follows a specific set of rules or guidelines governing how a game or activity is played.
-
E.
availableInMode
chosen
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.