Triple
T8621710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ericka Van Helsing |
E204181
|
entity |
| Predicate | laterAlignment |
P80575
|
FINISHED |
| Object | protagonistic |
—
|
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: protagonistic | Statement: [Ericka Van Helsing, laterAlignment, protagonistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAlignment Context triple: [Ericka Van Helsing, laterAlignment, protagonistic]
-
A.
successorAlignment
chosen
Indicates that one entity’s alignment, orientation, or configuration directly follows and is determined by that of another entity in a sequence or progression.
-
B.
previousAlignment
Indicates that one entity’s alignment or orientation occurred earlier in time than another’s.
-
C.
basedOnAlignmentOf
Indicates a relationship where one entity is determined, derived, or decided according to how closely it aligns with another entity’s position, orientation, or criteria.
-
D.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
E.
forceAlignment
Indicates that one entity compels another entity to match or conform its alignment, orientation, or position to its own or to a specified standard.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.