Triple
T4426161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Rosenworcel |
E95213
|
entity |
| Predicate | hasWorkedOnPolicy |
P55927
|
FINISHED |
| Object | net neutrality rules |
—
|
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: net neutrality rules | Statement: [Jessica Rosenworcel, hasWorkedOnPolicy, net neutrality rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkedOnPolicy Context triple: [Jessica Rosenworcel, hasWorkedOnPolicy, net neutrality rules]
-
A.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
B.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
C.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
-
D.
hasWorkDedicatedTo
Indicates that one entity has a work (such as a book, artwork, or composition) that is formally dedicated to another entity.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554fb28081909018eaecc0c5c230 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.