Triple
T37512624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldstone |
E932552
|
entity |
| Predicate | fragmentsProperty |
P189049
|
FINISHED |
| Object | retain reality-warping power |
—
|
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: retain reality-warping power | Statement: [Worldstone, fragmentsProperty, retain reality-warping power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragmentsProperty Context triple: [Worldstone, fragmentsProperty, retain reality-warping power]
-
A.
hasFragments
Indicates that an entity is composed of, contains, or is associated with one or more smaller constituent parts or pieces.
-
B.
preservesFragmentsOf
Indicates that one entity maintains, protects, or keeps intact partial remains or pieces of another entity.
-
C.
numberOfFragmentsApprox
Indicates an approximate count of how many fragments or pieces are associated with the subject.
-
D.
stoneFragmentsFrom
Indicates that one entity consists of or originates as stone fragments derived from another entity.
-
E.
nowFragmentedInto
Indicates that an entity that was once whole has been broken or divided into multiple separate parts or fragments.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.