Triple
T4833332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Decree of the Netherlands |
E107996
|
entity |
| Predicate | countersignedBy |
P9509
|
FINISHED |
| Object | responsible minister |
—
|
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: responsible minister | Statement: [Royal Decree of the Netherlands, countersignedBy, responsible minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countersignedBy Context triple: [Royal Decree of the Netherlands, countersignedBy, responsible minister]
-
A.
coSignedWith
chosen
Indicates that an entity has jointly signed a document, agreement, or obligation together with another entity.
-
B.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
C.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
signedTo
Indicates that one entity has formally entered into a contract or agreement with another, typically for representation, employment, or services.
-
E.
signerOf
Indicates that an entity has signed or formally endorsed a document, agreement, or statement.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.