Triple
T29427356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Manta |
E746330
|
entity |
| Predicate | causeOfFeudWithAquaman |
P61789
|
FINISHED |
| Object | death of Black Manta's father |
—
|
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: death of Black Manta's father | Statement: [Black Manta, causeOfFeudWithAquaman, death of Black Manta's father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfFeudWithAquaman Context triple: [Black Manta, causeOfFeudWithAquaman, death of Black Manta's father]
-
A.
hasCauseOfConflict
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
-
B.
causeOfVengeance
chosen
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
C.
feudedWith
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
D.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
-
E.
relationshipWithAntagonist
Indicates a relationship or connection that an entity has with an opposing or adversarial figure in a narrative or 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 3:10 p.m.