Triple
T28592963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Wikisource |
E723703
|
entity |
| Predicate | mobileSite |
P66849
|
FINISHED |
| Object | https://uk.m.wikisource.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://uk.m.wikisource.org | Statement: [Ukrainian Wikisource, mobileSite, https://uk.m.wikisource.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileSite Context triple: [Ukrainian Wikisource, mobileSite, https://uk.m.wikisource.org]
-
A.
mobileFriendly
Indicates that something (typically a website, app, or interface) is designed to function and display well on mobile devices.
-
B.
mobileVariant
chosen
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
C.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
D.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
E.
modernSiteCorrespondsTo
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
- 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_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:21 a.m.