Triple
T37110117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Man 3 (film score) |
E918963
|
entity |
| Predicate | successorInSeriesContext |
P13317
|
FINISHED |
| Object | The Amazing Spider-Man (film score) |
—
|
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: The Amazing Spider-Man (film score) | Statement: [Spider-Man 3 (film score), successorInSeriesContext, The Amazing Spider-Man (film score)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInSeriesContext Context triple: [Spider-Man 3 (film score), successorInSeriesContext, The Amazing Spider-Man (film score)]
-
A.
successorContext
Indicates that one context directly follows and continues from another in a sequence or process.
-
B.
successorSeries
chosen
Indicates that one series directly follows another in sequence, continuing or extending it as its successor.
-
C.
successorInPart
Indicates that one entity has taken over or continued a specific part or component of another entity, rather than succeeding it in its entirety.
-
D.
successorPowerContext
Indicates that one entity holds or exercises power or authority as a successor within a particular contextual or situational framework.
-
E.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00a602b6b48190a9dea8ae22d2fa05 |
completed | May 10, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_6a00a559bf3881909a7b50776d8f47bb |
completed | May 10, 2026, 3:33 p.m. |
Created at: May 3, 2026, 4:14 p.m.