Triple
T29205873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Stone |
E740409
|
entity |
| Predicate | counterpartInComics |
P182496
|
FINISHED |
| Object | Soul Gem |
—
|
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: Soul Gem | Statement: [Soul Stone, counterpartInComics, Soul Gem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterpartInComics Context triple: [Soul Stone, counterpartInComics, Soul Gem]
-
A.
fictionalCounterpartIn
Indicates that one entity serves as a fictional analogue or stand-in for another entity within a specified work or fictional universe.
-
B.
counterpartRelation
Indicates a reciprocal relationship where two entities serve as corresponding or equivalent counterparts to each other in a given context.
-
C.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
D.
isRelatedFictionalCounterpartTo
chosen
Indicates that one entity is the fictional or imagined counterpart, analogue, or version of another entity.
-
E.
comicFoilTo
Indicates that one character serves as a humorous contrast or counterpoint to another, enhancing the other’s traits or actions through comedic opposition or juxtaposition.
- 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_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: April 28, 2026, 12:09 p.m.