Triple
T322437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDI |
E6442
|
entity |
| Predicate | usedIn |
P98
|
FINISHED |
| Object | JTAG |
E1466
|
NE 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: JTAG | Statement: [TDI, usedIn, JTAG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JTAG Context triple: [TDI, usedIn, JTAG]
-
A.
IEEE 1149.1 JTAG boundary‑scan standard
chosen
The IEEE 1149.1 JTAG boundary-scan standard is a widely used test and debug specification that defines a serial interface and architecture for accessing and testing the internal logic and interconnects of integrated circuits and circuit boards.
-
B.
IEEE 1149.6
IEEE 1149.6 is a boundary-scan test standard that extends JTAG to support structural testing of high-speed AC-coupled and differential digital interconnects on printed circuit boards.
-
C.
IEEE 1149.7
IEEE 1149.7 is a compact, enhanced version of the JTAG test and debug standard that reduces pin count and power while adding advanced debug and trace capabilities for modern integrated circuits.
-
D.
JST
JST is the time zone used throughout Japan, nine hours ahead of Coordinated Universal Time (UTC+9).
-
E.
IEEE 488 GPIB standard
The IEEE 488 GPIB standard is a widely used digital interface specification that enables communication and control among electronic test and measurement instruments and computers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3cfe9c66c8190957b2ab7f5bae6fd |
completed | March 1, 2026, 5:34 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.