Triple
T29216099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Follow |
E740670
|
entity |
| Predicate | featuresProductPlacement |
P101226
|
FINISHED |
| Object | BMW automobiles |
—
|
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: BMW automobiles | Statement: [The Follow, featuresProductPlacement, BMW automobiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProductPlacement Context triple: [The Follow, featuresProductPlacement, BMW automobiles]
-
A.
featuresProductPlacementFor
chosen
Indicates that one entity includes or showcases another entity as a product placement within its content.
-
B.
sponsorPlacement
Indicates that one entity financially supports or endorses another entity in exchange for a specified form of promotional placement.
-
C.
featuresProductAnnouncement
Indicates that something includes or presents a product announcement as part of its content or offering.
-
D.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
E.
featuredOn
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: April 28, 2026, 12:13 p.m.