Triple
T109393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SnagFilms |
E2210
|
entity |
| Predicate | serviceAvailability |
P5871
|
FINISHED |
| Object | online globally (with regional restrictions) |
—
|
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: online globally (with regional restrictions) | Statement: [SnagFilms, serviceAvailability, online globally (with regional restrictions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAvailability Context triple: [SnagFilms, serviceAvailability, online globally (with regional restrictions)]
-
A.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
B.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
C.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563fd2fc819090265edbfe3092d6 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.