Triple
T8433696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Stones |
E199174
|
entity |
| Predicate | controlsAspectOfExistence |
P31808
|
FINISHED |
| Object | space |
—
|
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: space | Statement: [Infinity Stones, controlsAspectOfExistence, space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsAspectOfExistence Context triple: [Infinity Stones, controlsAspectOfExistence, space]
-
A.
ontologicalAspect
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
B.
governsAspectOf
chosen
Indicates that one entity exercises control, regulation, or determining influence over a particular aspect or component of another entity.
-
C.
cultAspect
Indicates that one entity represents a specific aspect, facet, or manifestation of a cult associated with another entity.
-
D.
viewOnThingInItself
Indicates a perspective or interpretation that considers an entity as it is in itself, independent of how it appears or is experienced.
-
E.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.