Triple
T28712854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki user rights system |
E729871
|
entity |
| Predicate | hasDefaultRight |
P191346
|
FINISHED |
| Object | read |
—
|
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: read | Statement: [MediaWiki user rights system, hasDefaultRight, read]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefaultRight Context triple: [MediaWiki user rights system, hasDefaultRight, read]
-
A.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasRightsFrom
Indicates that one entity possesses rights, permissions, or entitlements that originate from or are granted by another entity.
-
C.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
D.
hasUserRightsSystem
Indicates that an entity possesses or is associated with a system that manages or defines user access rights and permissions.
-
E.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 28, 2026, 5:49 a.m.