Triple
T38196606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Chaumont |
E1005632
|
entity |
| Predicate | createdAlliance |
P123274
|
FINISHED |
| Object | Quadruple Alliance of 1814 |
—
|
NE NERFINISHED |
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: Quadruple Alliance of 1814 | Statement: [Treaty of Chaumont, createdAlliance, Quadruple Alliance of 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAlliance Context triple: [Treaty of Chaumont, createdAlliance, Quadruple Alliance of 1814]
-
A.
allianceCreated
Indicates that a formal cooperative relationship or partnership has been established between two or more parties.
-
B.
formedAllianceThrough
chosen
Indicates that two or more parties established an alliance specifically by means of, or as a result of, a particular event, action, or intermediary.
-
C.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
newAlliancePattern
Indicates the formation of a new cooperative or strategic alliance pattern between entities.
-
E.
allianceStructure
Indicates the organizational or relational configuration that defines how members of an alliance are structured and interconnected.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:29 p.m.