Triple
T52647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interface Message Processor |
E1033
|
entity |
| Predicate | communicationMedium |
P1446
|
FINISHED |
| Object | leased telephone lines |
—
|
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: leased telephone lines | Statement: [Interface Message Processor, communicationMedium, leased telephone lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationMedium Context triple: [Interface Message Processor, communicationMedium, leased telephone lines]
-
A.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
usedInDigitalCommunication
chosen
Indicates that something is employed as a medium, tool, or element within digital or electronic communication processes.
-
C.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
-
D.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
-
E.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.