Triple
T20060380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Move (Radio Edit) |
E499454
|
entity |
| Predicate | editedFor |
P46107
|
FINISHED |
| Object | broadcast standards |
—
|
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: broadcast standards | Statement: [Move (Radio Edit), editedFor, broadcast standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editedFor Context triple: [Move (Radio Edit), editedFor, broadcast standards]
-
A.
editedIn
Indicates that an entity was modified, revised, or otherwise altered within a particular context, tool, environment, or time frame.
-
B.
editedOn
Indicates the date or time at which an entity was last modified or edited.
-
C.
editedLanguage
Indicates that one entity has revised, modified, or otherwise edited the language or linguistic content of another entity.
-
D.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
E.
amendedFor
chosen
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66374f4a48190beb575a6c84ebdb4 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.