Triple
T28565959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Cale |
E722677
|
entity |
| Predicate | broadcastAlias |
P168975
|
FINISHED |
| Object | Eyes Only |
E1824529
|
NE 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: Eyes Only | Statement: [Logan Cale, broadcastAlias, Eyes Only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastAlias Context triple: [Logan Cale, broadcastAlias, Eyes Only]
-
A.
broadcastVia
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
B.
broadcastFrom
Indicates that some content, signal, or message is transmitted or emitted starting at a particular source location, device, or entity.
-
C.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
D.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
E.
broadcastBand
Indicates that something is transmitted over a particular broadcast frequency band (e.g., AM, FM, VHF, UHF) for distribution to receivers.
- F. None of above. chosen
Provenance (5 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1ccf2c629481908123c7b8c4404a10 |
completed | June 1, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 28, 2026, 4:07 a.m.