Triple
T8993535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIX 03 |
E214845
|
entity |
| Predicate | governsUseOf |
P760
|
FINISHED |
| Object | UNIX trademark for certified systems |
—
|
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: UNIX trademark for certified systems | Statement: [UNIX 03, governsUseOf, UNIX trademark for certified systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsUseOf Context triple: [UNIX 03, governsUseOf, UNIX trademark for certified systems]
-
A.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
B.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
C.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc687798a881908e6fdd9a39219f1d |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.