Triple
T29407798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora Wiki |
E745814
|
entity |
| Predicate | editRights |
P166144
|
FINISHED |
| Object | registered Fedora contributors |
—
|
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: registered Fedora contributors | Statement: [Fedora Wiki, editRights, registered Fedora contributors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editRights Context triple: [Fedora Wiki, editRights, registered Fedora contributors]
-
A.
accessRight
chosen
Indicates that one entity has a specified permission or level of authorization to use, view, or interact with another entity or resource.
-
B.
editingPolicy
Indicates that one entity defines or enforces the rules, constraints, or procedures governing how another entity may be edited or modified.
-
C.
editingIs
Indicates that one entity is performing or undergoing the process of editing another entity.
-
D.
adminChange
Indicates that an administrative user performs or authorizes a modification to a system, resource, or configuration.
-
E.
modificationControl
Indicates that one entity has the authority or capability to alter, update, or otherwise change another entity or its properties.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a35eeb48190872f62f2e455ffee |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:55 p.m.