Triple
T322441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDI |
E6442
|
entity |
| Predicate | roleInTAP |
P268
|
FINISHED |
| Object | input pin to the test access port |
—
|
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: input pin to the test access port | Statement: [TDI, roleInTAP, input pin to the test access port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTAP Context triple: [TDI, roleInTAP, input pin to the test access port]
-
A.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
B.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
roleInEcosystem
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
E.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea82ba748190bae651f5de908617 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.