Triple
T6284375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAI |
E140861
|
entity |
| Predicate | secondaryFundingSource |
P69881
|
FINISHED |
| Object | advertising |
—
|
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: advertising | Statement: [RAI, secondaryFundingSource, advertising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryFundingSource Context triple: [RAI, secondaryFundingSource, advertising]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondaryFuel
Indicates that an entity uses or is associated with a secondary (additional or backup) fuel source in addition to its primary fuel.
-
C.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
-
D.
secondParty
Indicates that an entity participates in a relationship or transaction as the second party relative to a primary (first) party.
-
E.
possibleAdditionalFunding
Indicates that there is a potential for securing or providing further financial resources beyond what has already been allocated or committed.
- F. None of above. chosen
Provenance (4 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063fc906481908283c6c50a212515 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05b37ac1881909e947822490ba4f2 |
completed | March 22, 2026, 9:12 p.m. |
Created at: March 22, 2026, 4:26 p.m.