Triple
T38390598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Universe |
E899704
|
entity |
| Predicate | successorApproach |
P32861
|
FINISHED |
| Object | The Invisible Man (2020 film) |
—
|
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 Invisible Man (2020 film) | Statement: [Dark Universe, successorApproach, The Invisible Man (2020 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorApproach Context triple: [Dark Universe, successorApproach, The Invisible Man (2020 film)]
-
A.
successorInPractice
chosen
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
B.
successorAlgorithm
Indicates that one algorithm directly follows and replaces another in a sequence, versioning, or procedural progression.
-
C.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
D.
successorPolicy
Indicates that one policy follows or replaces another policy in a sequence or hierarchy.
-
E.
successorProtocol
Indicates that one protocol directly follows and replaces another in sequence or versioning.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
Created at: May 3, 2026, 4:31 p.m.