Triple
T21317132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph W. Fordney |
E525500
|
entity |
| Predicate | worked on |
P30363
|
FINISHED |
| Object | U.S. tariff legislation |
—
|
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: U.S. tariff legislation | Statement: [Joseph W. Fordney, worked on, U.S. tariff legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worked on Context triple: [Joseph W. Fordney, worked on, U.S. tariff legislation]
-
A.
workOn
chosen
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
B.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
-
C.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
-
D.
wonWork
Indicates that one party has successfully secured or been awarded a particular job, contract, or work opportunity over others.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dd0b34481909dd6d37cf8e42144 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:34 p.m.