Triple
T16817486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVM-300 |
E408790
|
entity |
| Predicate | signalIndicationForm |
P4618
|
FINISHED |
| Object | numeric speed codes |
—
|
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: numeric speed codes | Statement: [TVM-300, signalIndicationForm, numeric speed codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalIndicationForm Context triple: [TVM-300, signalIndicationForm, numeric speed codes]
-
A.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
B.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
C.
hasIndication
Indicates that one entity (typically a product, treatment, or intervention) is intended, approved, or suitable for use in addressing, preventing, or managing a particular condition, purpose, or circumstance.
-
D.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
-
E.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e30cf48190a61936ba0a49df24 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.