Triple
T32174177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scroll of the Ultimate |
E821790
|
entity |
| Predicate | valueToCharacters |
P72985
|
FINISHED |
| Object | immense |
—
|
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: immense | Statement: [Scroll of the Ultimate, valueToCharacters, immense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueToCharacters Context triple: [Scroll of the Ultimate, valueToCharacters, immense]
-
A.
perceivedAsByCharacters
Indicates how something is viewed, interpreted, or understood by one or more characters.
-
B.
representsForCharacters
Indicates that one entity performs a representation or advocacy role on behalf of specific characters.
-
C.
remainingCharactersRepresent
Indicates that the remaining characters in a string or sequence symbolize or stand for a particular value, concept, or entity.
-
D.
transformsCharacterInto
Indicates that one entity causes or undergoes a change that turns a character into another form, state, or identity.
-
E.
representsDigitsOf
chosen
Indicates that one entity encodes or corresponds to the individual digits that make up the numeric value of another entity.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:34 a.m.