Triple
T32798325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Shell maintainers team |
E838827
|
entity |
| Predicate | governsComponentOf |
P760
|
FINISHED |
| Object | GNOME desktop environment |
—
|
NE NERFINISHED |
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: GNOME desktop environment | Statement: [GNOME Shell maintainers team, governsComponentOf, GNOME desktop environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsComponentOf Context triple: [GNOME Shell maintainers team, governsComponentOf, GNOME desktop environment]
-
A.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
B.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
C.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to another entity.
-
D.
governsAspectOf
Indicates that one entity exercises control, regulation, or determining influence over a particular aspect or component of another entity.
-
E.
governedEntity
Indicates that one entity exercises authority, control, or governance over another entity.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
Created at: May 1, 2026, 1:14 a.m.