Triple
T2124488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsters, Inc. |
E46395
|
entity |
| Predicate | disneyPlusAvailability |
P3189
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Monsters, Inc., disneyPlusAvailability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disneyPlusAvailability Context triple: [Monsters, Inc., disneyPlusAvailability, yes]
-
A.
streamingService
chosen
Indicates that one entity provides or delivers media content over the internet to another entity in real time or on demand.
-
B.
laterAvailableInCountry
Indicates that something becomes available in a specified country at a later time than in other regions or than its initial release.
-
C.
bestSeenIn
Indicates that something is most effectively or appropriately experienced, observed, or appreciated within a particular context, medium, or setting.
-
D.
isPlayedIn
Indicates that an instance of a game, sport, or performance takes place within or is hosted at a particular location or venue.
-
E.
cateredBy
Indicates that an event, gathering, or service is provided with food and/or drink by a particular catering entity.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb55cb2c8190aab8199da3335032 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.