Triple
T16817465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVM-300 |
E408790
|
entity |
| Predicate | informationTransmission |
P4163
|
FINISHED |
| Object | track-to-train |
—
|
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: track-to-train | Statement: [TVM-300, informationTransmission, track-to-train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationTransmission Context triple: [TVM-300, informationTransmission, track-to-train]
-
A.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
-
B.
transmission
chosen
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
C.
technologyTransmitted
Indicates that some form of technology is passed or transferred from one entity to another.
-
D.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
-
E.
primaryTransmission
Indicates the main or original transfer of something (such as information, energy, or disease) from one source entity to another.
- 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.