Triple
T3719259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Confederation (1573) |
E81600
|
entity |
| Predicate | signatories |
P22092
|
FINISHED |
| Object | Polish nobility |
—
|
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: Polish nobility | Statement: [Warsaw Confederation (1573), signatories, Polish nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatories Context triple: [Warsaw Confederation (1573), signatories, Polish nobility]
-
A.
hasSignatories
chosen
Indicates that one or more parties have formally signed or endorsed an agreement, document, or instrument.
-
B.
numberOfSignatories
Indicates the total count of entities that have formally signed or endorsed a given document, agreement, or item.
-
C.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
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.
-
E.
signatoryGovernment
Indicates that a government is a formal signer or ratifying party to an agreement, treaty, or similar binding instrument.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca99e4248190a6a91808010b8b05 |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.