Triple
T35746982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juste une question d'amour |
E1033209
|
entity |
| Predicate | hasTypeOfBroadcast |
P160917
|
FINISHED |
| Object | television premiere |
—
|
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: television premiere | Statement: [Juste une question d'amour, hasTypeOfBroadcast, television premiere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfBroadcast Context triple: [Juste une question d'amour, hasTypeOfBroadcast, television premiere]
-
A.
hasBroadcastCategory
chosen
Indicates that an item is associated with a particular broadcast category or type of broadcast.
-
B.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
-
C.
hasBroadcastOrigin
Indicates the source location, channel, or medium from which a broadcast is originally transmitted.
-
D.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
E.
hasBroadcastStatus
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:06 p.m.