Triple
T29205875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Stone |
E740409
|
entity |
| Predicate | firstMCUMention |
P141957
|
FINISHED |
| Object | Guardians of the Galaxy |
—
|
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: Guardians of the Galaxy | Statement: [Soul Stone, firstMCUMention, Guardians of the Galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMCUMention Context triple: [Soul Stone, firstMCUMention, Guardians of the Galaxy]
-
A.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
B.
firstExplicitlyMentionedBy
Indicates that one entity is the earliest known source to explicitly mention or refer to another entity.
-
C.
mcuDebut
chosen
Indicates the work, appearance, or context in which a character or entity first appears within the Marvel Cinematic Universe.
-
D.
firstClearlyRecognizedIn
Indicates the point in time or context when something was first clearly identified, acknowledged, or distinguished as such.
-
E.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: April 28, 2026, 12:09 p.m.