Triple
T5479620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS |
E123437
|
entity |
| Predicate | transportsOver |
P53674
|
FINISHED |
| Object | control channel |
—
|
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: control channel | Statement: [SMS, transportsOver, control channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportsOver Context triple: [SMS, transportsOver, control channel]
-
A.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
B.
transportedOver
Indicates that something is moved or carried across or along a specified medium, route, or surface.
-
C.
transportInterface
chosen
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
D.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
E.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.