Triple
T12911666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.I.V.E. Five |
E308877
|
entity |
| Predicate | recurringRole |
P90709
|
FINISHED |
| Object | recurring antagonists |
—
|
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: recurring antagonists | Statement: [H.I.V.E. Five, recurringRole, recurring antagonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringRole Context triple: [H.I.V.E. Five, recurringRole, recurring antagonists]
-
A.
hasRecurringRole
chosen
Indicates that an entity repeatedly appears or participates in a role within an ongoing or multiple related contexts over time.
-
B.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
C.
continuityRole
Indicates that one entity serves a continuity-related function in relation to another, such as maintaining consistency or coherence across versions, segments, or states.
-
D.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
E.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719f96248190b746f9d4a468560c |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.