Triple
T18302132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pub.L. 73–416 |
E438381
|
entity |
| Predicate | regulatesMedium |
P70878
|
FINISHED |
| Object | wire communications |
—
|
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: wire communications | Statement: [Pub.L. 73–416, regulatesMedium, wire communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesMedium Context triple: [Pub.L. 73–416, regulatesMedium, wire communications]
-
A.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
B.
controlMedium
chosen
Indicates that an entity regulates, directs, or influences another entity through a particular medium or channel.
-
C.
regulatesWith
Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
-
D.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
-
E.
regulatesThrough
Indicates that one entity exerts control or influence over another by means of an intermediate mechanism, pathway, or process.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50180ac48819090e9a8f11ba10c3d |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.