Triple
T583686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutte II cabinet |
E15110
|
entity |
| Predicate | coalitionAgreementSigned |
P11095
|
FINISHED |
| Object | 2012-10-29 |
—
|
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: 2012-10-29 | Statement: [Rutte II cabinet, coalitionAgreementSigned, 2012-10-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionAgreementSigned Context triple: [Rutte II cabinet, coalitionAgreementSigned, 2012-10-29]
-
A.
TripartitePactSigned
Indicates that three distinct parties have formally agreed to and signed a mutual pact or treaty establishing a tripartite relationship.
-
B.
signatoryGovernment
chosen
Indicates that a government is a formal signer or ratifying party to an agreement, treaty, or similar binding instrument.
-
C.
signatoryBloc
Indicates that an entity is a member of, or aligned with, a specific bloc or group that has jointly signed or endorsed an agreement, treaty, or document.
-
D.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
E.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b8745c88190af9672e5fe8396c3 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.