Triple
T29655291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cybernetics Core |
E750246
|
entity |
| Predicate | unlocksUpgrade |
P168000
|
FINISHED |
| Object | Singularity Charge |
—
|
NE NERFINISHED |
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: Singularity Charge | Statement: [Cybernetics Core, unlocksUpgrade, Singularity Charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlocksUpgrade Context triple: [Cybernetics Core, unlocksUpgrade, Singularity Charge]
-
A.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
B.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
C.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
-
D.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
E.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 6:54 p.m.