Triple
T4557575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention Parliament |
E120515
|
entity |
| Predicate | sentDeclaration |
P36417
|
FINISHED |
| Object | invitation to Charles II at Breda |
—
|
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: invitation to Charles II at Breda | Statement: [Convention Parliament, sentDeclaration, invitation to Charles II at Breda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentDeclaration Context triple: [Convention Parliament, sentDeclaration, invitation to Charles II at Breda]
-
A.
declared
Indicates that an entity formally announces, states, or proclaims something, often with official or authoritative intent.
-
B.
sentDocumentTo
chosen
Indicates that one entity transmitted or delivered a document to another entity.
-
C.
statement
Indicates that an entity makes, issues, or expresses a declarative assertion, claim, or remark about something.
-
D.
signedFor
Indicates that one entity formally accepted or acknowledged receipt of something on behalf of another, typically by providing a signature.
-
E.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd58163e6081909d5a3aae12c42a00 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.