Triple
T37637977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King John II Casimir’s Lwów Oath |
E936539
|
entity |
| Predicate | includedPromise |
P134289
|
FINISHED |
| Object | social reforms |
—
|
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: social reforms | Statement: [King John II Casimir’s Lwów Oath, includedPromise, social reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPromise Context triple: [King John II Casimir’s Lwów Oath, includedPromise, social reforms]
-
A.
includesPromiseOf
chosen
Indicates that one entity contains or entails a commitment or assurance to perform or provide something to another entity.
-
B.
promisedIn
Indicates that one entity has made a commitment or assurance to perform an action or fulfill an obligation within the context or scope defined by another entity.
-
C.
keptPromiseTo
Indicates that one entity fulfilled or honored a promise previously made to another entity.
-
D.
promises
Indicates that one entity commits to performing, providing, or ensuring something for another entity in the future.
-
E.
corePromise
Indicates the primary commitment or central obligation that one party is bound to fulfill within an agreement or relationship.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.