Triple
T27731162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUS |
E697431
|
entity |
| Predicate | associatedTrademark |
P139092
|
FINISHED |
| Object | UNIX |
—
|
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: UNIX | Statement: [SUS, associatedTrademark, UNIX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTrademark Context triple: [SUS, associatedTrademark, UNIX]
-
A.
sharesTrademark
chosen
Indicates that two or more entities use or are associated with the same trademark.
-
B.
trademark
Indicates that one entity legally owns and uses a distinctive sign, name, or symbol to identify and distinguish its goods or services from those of others.
-
C.
trademarkAction
Indicates an action or legal event taken regarding a trademark, such as filing, registering, transferring, enforcing, or challenging trademark rights.
-
D.
visualTrademark
Indicates that one entity serves as a visual trademark or logo representing another entity.
-
E.
regulatesTrademark
Indicates that one entity has authority to control, oversee, or set rules governing the use or management of another entity’s trademark.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a0061454944819088a0babfe60f69fc |
completed | May 10, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_6a0060b9ee108190b91e8d99a16f2b30 |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 27, 2026, 3:11 p.m.