Triple
T29689579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragora GNU/Linux-Libre |
E751177
|
entity |
| Predicate | primaryTargetUsers |
P63093
|
FINISHED |
| Object | advanced GNU/Linux users |
—
|
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: advanced GNU/Linux users | Statement: [Dragora GNU/Linux-Libre, primaryTargetUsers, advanced GNU/Linux users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTargetUsers Context triple: [Dragora GNU/Linux-Libre, primaryTargetUsers, advanced GNU/Linux users]
-
A.
primaryUsersOf
Indicates that the subject is the main or most frequent user(s) of the object.
-
B.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
E.
primaryUserType
chosen
Indicates the main or dominant category of user associated with an entity or interaction.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
Created at: April 28, 2026, 7:15 p.m.