Triple
T28594714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Wikipedia |
E723741
|
entity |
| Predicate | mobileURL |
P66849
|
FINISHED |
| Object | https://sr.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://sr.m.wikipedia.org | Statement: [Serbian Wikipedia, mobileURL, https://sr.m.wikipedia.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileURL Context triple: [Serbian Wikipedia, mobileURL, https://sr.m.wikipedia.org]
-
A.
mobileVariant
chosen
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
B.
accessURL
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
C.
socialLink
Indicates that there exists a social relationship or connection between the referenced entities, such as friendship, following, or other social-network ties.
-
D.
mobileFriendly
Indicates that something (typically a website, app, or interface) is designed to function and display well on mobile devices.
-
E.
hadURL
Indicates that an entity was associated with or linked to a specific URL at some point in time.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:21 a.m.