Triple
T9317144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David (Alien franchise) |
E224151
|
entity |
| Predicate | roleInAlienCovenant |
P88049
|
FINISHED |
| Object | antagonist |
—
|
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: antagonist | Statement: [David (Alien franchise), roleInAlienCovenant, antagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAlienCovenant Context triple: [David (Alien franchise), roleInAlienCovenant, antagonist]
-
A.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
B.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
C.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
D.
roleInCyborgOrigin
Indicates that an entity plays a specific role in the origin, creation, or transformation process that results in a cyborg.
-
E.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd35899b9081908bb0c310cc25722f |
completed | April 1, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:38 p.m.