Triple
T13745876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Hermano (Spain) |
E330208
|
entity |
| Predicate | hasLiveFeed |
P80381
|
FINISHED |
| Object | pay television channels |
—
|
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: pay television channels | Statement: [Gran Hermano (Spain), hasLiveFeed, pay television channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveFeed Context triple: [Gran Hermano (Spain), hasLiveFeed, pay television channels]
-
A.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
B.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
C.
offersLiveStreaming
chosen
Indicates that one entity provides the capability for real-time (live) streaming of content to another entity or audience.
-
D.
hasLiveFeel
Indicates that something possesses a vivid, dynamic, or lifelike quality or atmosphere.
-
E.
isFrequentlyRecordedLive
Indicates that the subject is often captured or documented in live recordings, such as live performances, broadcasts, or real-time sessions.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0211ba5481909fbd5b447e3d5a02 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.