Triple
T35422551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special World |
E1023831
|
entity |
| Predicate | saveDataEffect |
P172313
|
FINISHED |
| Object | completion marked on save file star counter |
—
|
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: completion marked on save file star counter | Statement: [Special World, saveDataEffect, completion marked on save file star counter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saveDataEffect Context triple: [Special World, saveDataEffect, completion marked on save file star counter]
-
A.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
B.
scoreEffect
Indicates the impact or change that an action, event, or condition has on a score or scoring outcome.
-
C.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
D.
capturesEffectOf
chosen
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
-
E.
savedWhile
Indicates that one entity was saved or preserved during the time another event or action was occurring.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7958d59388190a937ac6f4c81d3c9 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.