Triple
T28643967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew Wikiversity |
E725002
|
entity |
| Predicate | supportsMultimediaContent |
P74462
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hebrew Wikiversity, supportsMultimediaContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultimediaContent Context triple: [Hebrew Wikiversity, supportsMultimediaContent, true]
-
A.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
B.
supportsOnlineContent
chosen
Indicates that one entity provides the infrastructure, functionality, or capability for another entity to host, deliver, or interact with content over the internet.
-
C.
supportsMediaManagement
Indicates that one entity provides functionality or assistance for organizing, handling, or controlling media content for another entity.
-
D.
mediaSupportFrom
Indicates that one entity provides media-related backing, coverage, or promotional support to another entity.
-
E.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01b935e3948190a7af37b07938d618 |
completed | May 11, 2026, 11:10 a.m. |
| PD | Predicate disambiguation | batch_6a01b8d198b48190b01e16ac9ce7e7bd |
completed | May 11, 2026, 11:09 a.m. |
Created at: April 28, 2026, 4:47 a.m.