Triple
T26942824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kree Empire |
E678563
|
entity |
| Predicate | MCUFilmAppearance |
P91475
|
FINISHED |
| Object | Guardians of the Galaxy Vol. 2 (indirectly) |
—
|
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 Vol. 2 (indirectly) | Statement: [Kree Empire, MCUFilmAppearance, Guardians of the Galaxy Vol. 2 (indirectly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MCUFilmAppearance Context triple: [Kree Empire, MCUFilmAppearance, Guardians of the Galaxy Vol. 2 (indirectly)]
-
A.
MCUFilm
Indicates that a film is part of the Marvel Cinematic Universe franchise.
-
B.
MCUFamily
Indicates a familial relationship between entities within the Marvel Cinematic Universe (MCU), such as by blood, marriage, or adoption.
-
C.
marvelCinematicUniverseDebutFilm
Indicates the film in which an entity (such as a character or actor) first appeared within the Marvel Cinematic Universe.
-
D.
speciesInMCU
chosen
Indicates that a given species exists or appears within the Marvel Cinematic Universe.
-
E.
MCUStoryArc
Indicates a narrative relationship where events or elements are part of the same overarching Marvel Cinematic Universe story arc.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:19 a.m.