Triple
T1180315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPON |
E25120
|
entity |
| Predicate | upstreamBitrate |
P1376
|
FINISHED |
| Object | up to 1.244 Gbit/s |
—
|
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: up to 1.244 Gbit/s | Statement: [GPON, upstreamBitrate, up to 1.244 Gbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upstreamBitrate Context triple: [GPON, upstreamBitrate, up to 1.244 Gbit/s]
-
A.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
videoQuality
Indicates the level or standard of clarity, resolution, and overall visual fidelity associated with a given video.
-
C.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
D.
transmissionDuration
Indicates the length of time over which a transmission or transfer of data, signal, or content occurs.
-
E.
pegRatio
Indicates the relationship between a company’s price-to-earnings (P/E) ratio and its expected earnings growth rate, expressing how highly the market values each unit of anticipated growth.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.