Triple
T29205876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Stone |
E740409
|
entity |
| Predicate | locationRequirementInMCU |
P201589
|
FINISHED |
| Object | sacrifice of a loved one |
—
|
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: sacrifice of a loved one | Statement: [Soul Stone, locationRequirementInMCU, sacrifice of a loved one]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRequirementInMCU Context triple: [Soul Stone, locationRequirementInMCU, sacrifice of a loved one]
-
A.
locationRequirement
Indicates that a specific location or type of place is required or must be satisfied for an action, condition, or relationship to hold.
-
B.
locationOnKit
Indicates that an entity is located on or attached to a specific kit or equipment set.
-
C.
locationOnDevice
Indicates that one entity is stored or situated on a particular device.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
| PDg | Predicate description generation | batch_6a000a1c8f8881908293ab4f7207d25f |
completed | May 10, 2026, 4:31 a.m. |
Created at: April 28, 2026, 12:09 p.m.