Triple
T28631201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Wikipedia |
E724642
|
entity |
| Predicate | hasUserRightsSystem |
P166232
|
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: [Ukrainian Wikipedia, hasUserRightsSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserRightsSystem Context triple: [Ukrainian Wikipedia, hasUserRightsSystem, true]
-
A.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
C.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
D.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
E.
hasAccessBy
Indicates that one entity is permitted to access, use, or interact with another entity, typically under specified permissions or conditions.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 4:37 a.m.