Triple
T16866322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8MM 2 |
E410047
|
entity |
| Predicate | narrativeRelationTo |
P51756
|
FINISHED |
| Object | continues themes of 8MM |
—
|
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: continues themes of 8MM | Statement: [8MM 2, narrativeRelationTo, continues themes of 8MM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRelationTo Context triple: [8MM 2, narrativeRelationTo, continues themes of 8MM]
-
A.
narrativeConnection
chosen
Indicates a meaningful relationship between elements within a narrative, such as events, characters, or scenes, that links them in terms of plot, causality, or thematic continuity.
-
B.
associatedWithPersonInStory
Indicates that one entity has a connection or involvement with a specific person within the context of a story.
-
C.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
D.
narrativeSubject
Indicates that an entity functions as the main subject or focal point within a narrative or story.
-
E.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b5088f208190abfe937633ebe3fe |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.