Triple
T33631983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Acosta |
E861587
|
entity |
| Predicate | laterAppearsOnPlatform |
P28313
|
FINISHED |
| Object | Paramount+ |
—
|
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: Paramount+ | Statement: [David Acosta, laterAppearsOnPlatform, Paramount+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAppearsOnPlatform Context triple: [David Acosta, laterAppearsOnPlatform, Paramount+]
-
A.
appearsInPlatform
Indicates that an entity is present, available, or featured within a particular platform or system.
-
B.
laterAppearsOnNetwork
chosen
Indicates that an entity is broadcast or becomes available on a specified network at a later time than some reference point or initial appearance.
-
C.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
-
D.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
E.
laterPlatform
Indicates that one entity occurs, appears, or is positioned on a platform that comes after another platform in time or sequence.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 1, 2026, 1:41 a.m.