Triple
T23497312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTTH |
E571735
|
entity |
| Predicate | deploymentDriver |
P152614
|
FINISHED |
| Object | increasing bandwidth demand |
—
|
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: increasing bandwidth demand | Statement: [FTTH, deploymentDriver, increasing bandwidth demand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentDriver Context triple: [FTTH, deploymentDriver, increasing bandwidth demand]
-
A.
densityDriver
Indicates a factor or agent that directly influences or determines the density of something.
-
B.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
C.
deploymentOption
Indicates the available or chosen way in which something (such as a system, service, or component) can be deployed or made operational.
-
D.
typeOfDeployment
Indicates the specific manner or configuration in which something (such as a system, application, or resource) is deployed or made operational.
-
E.
deploymentSource
Indicates the origin or mechanism from which something is deployed, such as the system, process, or source responsible for initiating the deployment.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e0c5a48190badb8303f40f6180 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:05 p.m.