Triple
T1105033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Fiber |
E25468
|
entity |
| Predicate | dataTransmission |
P7413
|
FINISHED |
| Object | light over fiber |
—
|
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: light over fiber | Statement: [AT&T Fiber, dataTransmission, light over fiber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTransmission Context triple: [AT&T Fiber, dataTransmission, light over fiber]
-
A.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
B.
dataTransferType
Indicates the method or mode by which data is transmitted or exchanged between entities.
-
C.
isTransmittedBy
Indicates that something (such as information, a signal, or a disease) is passed or conveyed from one entity to another through a specified agent or medium.
-
D.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
E.
transmissionType
chosen
Indicates the method or medium through which something is transmitted or conveyed from one 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e21f048190bf4b63dd2c7c7641 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.