Triple
T6230233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Even Flow |
E139333
|
entity |
| Predicate | hasAlternateRecording |
P57506
|
FINISHED |
| Object | re-recorded single version |
—
|
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: re-recorded single version | Statement: [Even Flow, hasAlternateRecording, re-recorded single version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateRecording Context triple: [Even Flow, hasAlternateRecording, re-recorded single version]
-
A.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
B.
laterRecordedIn
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
-
C.
hasAlternateCut
chosen
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
hasReprise
Indicates that an action, theme, or element is repeated or returns after its initial occurrence.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d9a33c8190b66dbd89e0e3bbba |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.