Triple
T322456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDI |
E6442
|
entity |
| Predicate | relatedSignal |
P37
|
FINISHED |
| Object | TMS |
E6441
|
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: TMS | Statement: [TDI, relatedSignal, TMS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TMS Context triple: [TDI, relatedSignal, TMS]
-
A.
TMS
chosen
TMS (Test Mode Select) is the JTAG control signal used to navigate the TAP (Test Access Port) state machine in IEEE 1149.1 boundary-scan operations.
-
B.
MNE
MNE is the standard abbreviation used for the Maine Celtics, an NBA G League basketball team based in Portland, Maine.
-
C.
the T
The T is the public transit system serving the Greater Boston area, operated by the Massachusetts Bay Transportation Authority.
-
D.
NMTI
NMTI is a prestigious United States presidential award that honors individuals, teams, and companies for outstanding contributions to technological innovation and advancement.
-
E.
NMTI
NMTI is an acronym whose specific meaning depends on context, commonly referring to various technical or institutional names.
- 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_69a2ee028c488190ad0109510de2956d |
completed | Feb. 28, 2026, 1:30 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.