Triple
T29066241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenderness |
E735681
|
entity |
| Predicate | featuresReimaginedVersionsOf |
P27793
|
FINISHED |
| Object | We Got By |
—
|
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: We Got By | Statement: [Tenderness, featuresReimaginedVersionsOf, We Got By]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresReimaginedVersionsOf Context triple: [Tenderness, featuresReimaginedVersionsOf, We Got By]
-
A.
featuresReimaginedVersionOf
chosen
Indicates that something includes or presents a newly interpreted or updated version of another existing work or element.
-
B.
containsReimaginedVersionsOf
Indicates that one entity includes or incorporates updated, reinterpreted, or newly imagined versions of another entity.
-
C.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
D.
appearsInRemakeAs
Indicates that an entity reappears in a remake version of a work, typically in a similar or related role as in the original.
-
E.
filmCharacterVersionOf
Indicates that one character is a specific film adaptation or portrayal of another character originating from a different version or medium.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: April 28, 2026, 10:18 a.m.