Triple
T16381060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William A. Nitze |
E397805
|
entity |
| Predicate | influencesDomain |
P121917
|
FINISHED |
| Object | international climate negotiations |
—
|
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: international climate negotiations | Statement: [William A. Nitze, influencesDomain, international climate negotiations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencesDomain Context triple: [William A. Nitze, influencesDomain, international climate negotiations]
-
A.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
B.
affectedDomain
chosen
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
C.
placeOfInfluence
Indicates the location or area where an entity exerts significant impact, authority, or cultural, social, or intellectual influence.
-
D.
influencesFocus
Indicates that one entity affects or shapes the attention, concentration, or focal priorities of another entity.
-
E.
involvedDomain
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319db5b648190a8fca23518a1fb39 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.