Triple
T36908046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Access Port |
E912830
|
entity |
| Predicate | interpretsControlSignal |
P151612
|
FINISHED |
| Object | TMS |
—
|
NE NERFINISHED |
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: [Test Access Port, interpretsControlSignal, TMS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretsControlSignal Context triple: [Test Access Port, interpretsControlSignal, TMS]
-
A.
controlSignals
Indicates that one entity sends or governs directive signals that determine or influence the behavior or operation of another entity.
-
B.
recognizedControlOf
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control over something.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
controlsBehaviorOf
Indicates that one entity has the power or mechanism to direct, regulate, or determine the behavior of another entity.
-
E.
detectsSignalType
chosen
Indicates that an entity identifies or recognizes the specific type or category of a given signal.
- 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_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:13 p.m.