Triple
T2364173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Decision to Intervene |
E47342
|
entity |
| Predicate | usesSourceType |
P38247
|
FINISHED |
| Object | diplomatic correspondence |
—
|
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: diplomatic correspondence | Statement: [The Decision to Intervene, usesSourceType, diplomatic correspondence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSourceType Context triple: [The Decision to Intervene, usesSourceType, diplomatic correspondence]
-
A.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
B.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
D.
isMajorSourceOf
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc746e7048190a09a38401b367628 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6a85e2c8190afec217ff29476be |
completed | March 7, 2026, 6:33 a.m. |
Created at: March 4, 2026, 7:55 p.m.