Triple
T5725676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustus II the Strong |
E126257
|
entity |
| Predicate | conversionReason |
P45854
|
FINISHED |
| Object | to become King of Poland |
—
|
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: to become King of Poland | Statement: [Augustus II the Strong, conversionReason, to become King of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionReason Context triple: [Augustus II the Strong, conversionReason, to become King of Poland]
-
A.
reasonForConversion
chosen
Indicates the cause, motivation, or justification behind a particular conversion event or change.
-
B.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
D.
conversionPolicy
Indicates the rules or conditions that govern how one thing is converted or transformed into another.
-
E.
conversionStatus
Indicates the current state or outcome of a process in which one entity is transformed, converted, or transitioned into another form or status.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.