Triple
T17301659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flint Marko |
E420052
|
entity |
| Predicate | sometimesAlignedAs |
P126902
|
FINISHED |
| Object | antihero |
—
|
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: antihero | Statement: [Flint Marko, sometimesAlignedAs, antihero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesAlignedAs Context triple: [Flint Marko, sometimesAlignedAs, antihero]
-
A.
laterAlignedWith
Indicates that one entity becomes aligned with or matches another entity at a later point in time, rather than initially.
-
B.
notAlignedWith
Indicates that one entity’s position, orientation, or viewpoint does not correspond or agree with that of another entity.
-
C.
originallyAlignedWith
Indicates that an entity was initially in agreement, support, or association with another entity or group, regardless of any later changes in stance or affiliation.
-
D.
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.
-
E.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fae8848190a06c5866e606baac |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:41 a.m.