Triple
T28712844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki user rights system |
E729871
|
entity |
| Predicate | hasDefaultGroup |
P23187
|
FINISHED |
| Object | * |
—
|
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: * | Statement: [MediaWiki user rights system, hasDefaultGroup, *]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefaultGroup Context triple: [MediaWiki user rights system, hasDefaultGroup, *]
-
A.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
B.
hasCentralGroup
chosen
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
C.
hasKeyGroup
Indicates that an entity is associated with a particular key group that governs or organizes its access, classification, or control.
-
D.
hasRepresentativeGroup
Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
-
E.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 5:49 a.m.