Triple
T34192859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 99 |
E877156
|
entity |
| Predicate | hasSuperpowerSource |
P61281
|
FINISHED |
| Object | Noor stones |
—
|
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: Noor stones | Statement: [The 99, hasSuperpowerSource, Noor stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperpowerSource Context triple: [The 99, hasSuperpowerSource, Noor stones]
-
A.
hasSuperpower
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
B.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
C.
hasAbilitySource
Indicates that an entity’s ability originates from, or is derived through, a specified source.
-
D.
hasSuperpowersTheme
Indicates that the subject involves, features, or centers around the theme of characters possessing superhuman abilities or powers.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 1, 2026, 1:55 a.m.