Triple
T26092795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Swing Ding |
E658170
|
entity |
| Predicate | primaryUserAlignment |
P2562
|
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: [Wild Swing Ding, primaryUserAlignment, antihero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserAlignment Context triple: [Wild Swing Ding, primaryUserAlignment, antihero]
-
A.
primaryAlignment
chosen
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
-
B.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
C.
primaryUserIntended
Indicates that the referenced user is the main or originally intended user associated with the action, resource, or context.
-
D.
primaryUserDesignation
Indicates that one user is designated as the main or primary user among multiple associated users.
-
E.
policyAlignment
Indicates the degree to which one entity’s policies are consistent with, supportive of, or in agreement with those of another entity.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 26, 2026, 7:48 p.m.