Triple
T31317601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Hero (Roosevelt Remix) |
E798637
|
entity |
| Predicate | retainsElementsFrom |
P145521
|
FINISHED |
| Object | Anti-Hero |
—
|
NE NERFINISHED |
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: Anti-Hero | Statement: [Anti-Hero (Roosevelt Remix), retainsElementsFrom, Anti-Hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainsElementsFrom Context triple: [Anti-Hero (Roosevelt Remix), retainsElementsFrom, Anti-Hero]
-
A.
retainsElementFrom
chosen
Indicates that one entity keeps or preserves an element that originates from another entity.
-
B.
retainsElementInSuccessor
Indicates that a specific element present in one state, version, or step is preserved and remains present in its immediate successor.
-
C.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
D.
proposedToRetain
Indicates that one entity has suggested or decided to keep or continue maintaining another entity in its current role, state, or possession.
-
E.
retainsFromPreviousArms
Indicates that an entity keeps or carries over characteristics, components, or configurations from its earlier arm versions or states.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.