Triple
T13782437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pen Register Act |
E331162
|
entity |
| Predicate | technologyScope |
P74633
|
FINISHED |
| Object | telecommunications networks |
—
|
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: telecommunications networks | Statement: [Pen Register Act, technologyScope, telecommunications networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyScope Context triple: [Pen Register Act, technologyScope, telecommunications networks]
-
A.
technologyField
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyContext
chosen
Indicates the technological setting, tools, or systems within which an action, relationship, or process occurs.
-
D.
technologyTrend
Indicates a relationship where a technology is characterized as part of a broader pattern of change or direction in technological development over time.
-
E.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0247ccc881908dad7b547221f15d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.