Triple
T322408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMS |
E6441
|
entity |
| Predicate | usedToNavigate |
P11421
|
FINISHED |
| Object | TAP (Test Access Port) state machine |
—
|
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: TAP (Test Access Port) state machine | Statement: [TMS, usedToNavigate, TAP (Test Access Port) state machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToNavigate Context triple: [TMS, usedToNavigate, TAP (Test Access Port) state machine]
-
A.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
B.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
C.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
D.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- F. None of above. chosen
Provenance (4 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. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.