Triple
T36908049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Access Port |
E912830
|
entity |
| Predicate | mayIncludeResetSignal |
P53912
|
FINISHED |
| Object | TRST |
—
|
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: TRST | Statement: [Test Access Port, mayIncludeResetSignal, TRST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeResetSignal Context triple: [Test Access Port, mayIncludeResetSignal, TRST]
-
A.
mayIncludeMode
Indicates that one entity is allowed to contain or support a particular mode as one of its possible configurations or options.
-
B.
mayIncludeFeature
chosen
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
C.
mayAlsoInclude
Indicates that something can optionally contain or encompass additional elements beyond those primarily specified.
-
D.
mayIncludePower
Indicates that something is permitted or able to contain, involve, or provide power as one of its possible components or attributes.
-
E.
mayIncludeRequirement
Indicates that something can optionally contain or encompass a particular requirement as part of its definition or structure.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdac94a0819090d0dd980eb38377 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.