Triple
T23773774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Envole-moi |
E587612
|
entity |
| Predicate | isFrequentlyBroadcastOn |
P62249
|
FINISHED |
| Object | French radio |
—
|
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: French radio | Statement: [Envole-moi, isFrequentlyBroadcastOn, French radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyBroadcastOn Context triple: [Envole-moi, isFrequentlyBroadcastOn, French radio]
-
A.
isFrequentlyBroadcastDuring
Indicates that one entity (such as a program, advertisement, or message) is regularly aired or transmitted during another entity (such as a specific time slot, event, or show).
-
B.
hasRegularBroadcastFrequency
Indicates that an entity maintains a consistent, recurring schedule or rate at which it broadcasts.
-
C.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
D.
oftenBroadcastBy
chosen
Indicates that something (such as a program, message, or content) is frequently transmitted or aired by a particular broadcaster or channel.
-
E.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c468fb948190baa66a4353f0ca71 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.