Triple
T33917405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkan |
E869498
|
entity |
| Predicate | broadcastNetworkContext |
P125922
|
FINISHED |
| Object | ABC |
—
|
NE NERFINISHED |
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: ABC | Statement: [Orkan, broadcastNetworkContext, ABC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastNetworkContext Context triple: [Orkan, broadcastNetworkContext, ABC]
-
A.
broadcastContext
chosen
Indicates that an entity disseminates information, content, or signals to multiple recipients within a particular situational or environmental setting.
-
B.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
C.
broadcastNetworkType
Indicates the type or category of broadcast network through which content is transmitted or distributed.
-
D.
broadcastNetworkTypical
Indicates that a given broadcast network is the one typically or commonly associated with airing the specified content or program.
-
E.
broadcastRuntime
Indicates that an entity transmits or distributes content or data during its execution period or operational timeframe.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:48 a.m.