Triple
T9317145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David (Alien franchise) |
E224151
|
entity |
| Predicate | roleInPrometheus |
P88050
|
FINISHED |
| Object | supporting character |
—
|
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: supporting character | Statement: [David (Alien franchise), roleInPrometheus, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPrometheus Context triple: [David (Alien franchise), roleInPrometheus, supporting character]
-
A.
roleInPrometheusBound
Indicates that an entity has a specific role or character assignment in the work *Prometheus Bound*.
-
B.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
gammaRole
Indicates a tertiary or supporting role that an entity plays within a structured hierarchy of roles or participants in an event or relationship.
-
E.
roleInCluster
Indicates the specific function or position an entity holds within a defined group or cluster of related entities.
- 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.