Triple
T29205891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Stone |
E740409
|
entity |
| Predicate | inCombinationWith |
P131235
|
FINISHED |
| Object | Space Stone |
—
|
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: Space Stone | Statement: [Soul Stone, inCombinationWith, Space Stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCombinationWith Context triple: [Soul Stone, inCombinationWith, Space Stone]
-
A.
typicalCombinationWith
chosen
Indicates that one entity is commonly or characteristically used, found, or occurs together in combination with another entity.
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
laterCombination
Indicates that one entity is a combination or composite that occurs after, or is formed subsequent to, another entity or state.
-
D.
introducedFromCombinationOf
Indicates that something is newly created or arises as a result of combining two or more other entities or elements.
-
E.
actedTogetherWith
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:09 p.m.