Triple
T9762870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Man 2 |
E236709
|
entity |
| Predicate | hasFightSceneWith |
P90892
|
FINISHED |
| Object | Spider-Man vs Doctor Octopus |
—
|
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: Spider-Man vs Doctor Octopus | Statement: [Spider-Man 2, hasFightSceneWith, Spider-Man vs Doctor Octopus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFightSceneWith Context triple: [Spider-Man 2, hasFightSceneWith, Spider-Man vs Doctor Octopus]
-
A.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
B.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
C.
hasGunfights
Indicates that there are one or more gunfights occurring between the related entities.
-
D.
hasDanceSceneWith
Indicates that two entities participate together in a dance scene within the same context or work.
-
E.
hasCutscenes
Indicates that the subject includes or features one or more non-interactive cinematic sequences (cutscenes).
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda09d8bc88190808145f141b4a9f8 |
completed | April 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:25 p.m.