Triple
T23042234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS 44-series |
E573766
|
entity |
| Predicate | governsInterface |
P148363
|
FINISHED |
| Object | Um interface |
—
|
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: Um interface | Statement: [TS 44-series, governsInterface, Um interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsInterface Context triple: [TS 44-series, governsInterface, Um interface]
-
A.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
B.
governsSectionOf
Indicates that one entity has authoritative control or regulatory oversight over a specific section or part of another entity.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
definesInterfaceProtocol
chosen
Indicates that one entity specifies or establishes the communication or interaction protocol that another entity must follow as its interface.
-
E.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18516417081908bf747b20de23a75 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.