Triple
T28593042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrew Wikipedia |
E723705
|
entity |
| Predicate | mobileWebsite |
P66849
|
FINISHED |
| Object | https://he.m.wikipedia.org |
—
|
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: https://he.m.wikipedia.org | Statement: [Hebrew Wikipedia, mobileWebsite, https://he.m.wikipedia.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileWebsite Context triple: [Hebrew Wikipedia, mobileWebsite, https://he.m.wikipedia.org]
-
A.
mobileFriendly
Indicates that something (typically a website, app, or interface) is designed to function and display well on mobile devices.
-
B.
website
Indicates that one entity is the official website or web presence associated with another entity.
-
C.
webType
Indicates the classification or category of a web resource or web-related entity (such as its type, role, or format) within a given context.
-
D.
webPage
Indicates that one entity is a web page associated with, describing, or providing information about another entity.
-
E.
mobileVariant
chosen
Indicates that one entity is a mobile-specific version or adaptation of another 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:21 a.m.