Triple
T641733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Foreign Trade Council |
E16752
|
entity |
| Predicate | hasAdvocacyArea |
P11461
|
FINISHED |
| Object | tariff policy |
—
|
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: tariff policy | Statement: [National Foreign Trade Council, hasAdvocacyArea, tariff policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvocacyArea Context triple: [National Foreign Trade Council, hasAdvocacyArea, tariff policy]
-
A.
hasPolicyArea
Indicates that an entity (such as a policy, program, or initiative) is associated with or pertains to a specific policy area or domain.
-
B.
areaOfActivism
chosen
Indicates the specific social, political, or environmental cause or issue that an entity actively advocates for or works to change.
-
C.
coversPolicyArea
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
D.
hasLegislativeSubject
Indicates that a legislative document, action, or body concerns, addresses, or is about a particular subject or topic.
-
E.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f02bc2c8190b8a92b2505768c19 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.