Triple
T37508136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Table |
E932148
|
entity |
| Predicate | offlineProgression |
P188178
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Command Table, offlineProgression, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offlineProgression Context triple: [Command Table, offlineProgression, true]
-
A.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
B.
playerProgressionFrom
Indicates a progression or advancement of a player from one state, level, or stage to another.
-
C.
hasProgressionSystem
Indicates that an entity includes or is associated with a structured system through which progress, advancement, or development can occur over time.
-
D.
multiplayerProgression
Indicates that multiple participants advance or develop together over time within a shared activity or system.
-
E.
trainingProgression
Indicates the advancement or change in a subject’s training status over time, typically reflecting movement from earlier to later stages of a training process.
- F. None of above. chosen
Provenance (4 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.