Triple
T5479504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMT-2000 family |
E123435
|
entity |
| Predicate | radioInterfaceFamily |
P64019
|
FINISHED |
| Object | IMT-DS |
—
|
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: IMT-DS | Statement: [IMT-2000 family, radioInterfaceFamily, IMT-DS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioInterfaceFamily Context triple: [IMT-2000 family, radioInterfaceFamily, IMT-DS]
-
A.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
B.
protocolFamily
Indicates that one protocol belongs to, or is categorized under, a broader protocol family or group.
-
C.
addressFamily
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
-
D.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
E.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
- 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_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. |
| PDg | Predicate description generation | batch_69bd9214b8488190979112c7615f359a |
completed | March 20, 2026, 6:29 p.m. |
Created at: March 20, 2026, 2:09 p.m.