Triple
T36923442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnage |
E913269
|
entity |
| Predicate | parentSymbiote |
P196682
|
FINISHED |
| Object | Venom |
—
|
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: Venom | Statement: [Carnage, parentSymbiote, Venom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentSymbiote Context triple: [Carnage, parentSymbiote, Venom]
-
A.
parentPublisher
Indicates that one publisher entity is the direct parent or owning publisher of another publisher entity.
-
B.
parentService
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
-
C.
symbiontDependency
Indicates that one symbiotic partner depends on the other for survival, resources, or essential functions within their symbiotic relationship.
-
D.
parentCometType
Indicates the type or classification of the comet from which another object (such as a meteor stream or fragment) originates.
-
E.
parentAct
Indicates that one entity performs an action in the role of a parent toward another entity, typically involving caregiving, guidance, or parental responsibility.
- F. None of above. chosen
Provenance (4 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:13 p.m.