Triple
T17625533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regency Kingdom of Poland |
E429830
|
entity |
| Predicate | intendedMonarch |
P38852
|
FINISHED |
| Object | unspecified king to be chosen later |
—
|
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: unspecified king to be chosen later | Statement: [Regency Kingdom of Poland, intendedMonarch, unspecified king to be chosen later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMonarch Context triple: [Regency Kingdom of Poland, intendedMonarch, unspecified king to be chosen later]
-
A.
monarchSheIsHeirTo
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
-
B.
monarchInQuestion
Indicates that the referenced entity is the specific monarch being discussed or evaluated in the given context.
-
C.
laterMonarch
Indicates that one monarch’s reign occurred after another monarch’s reign in time.
-
D.
proposedMonarch
chosen
Indicates that one entity has been put forward or nominated to become the monarch or ruler of another entity.
-
E.
representedMonarch
Indicates that one entity formally acted on behalf of, or served as the official representative of, a monarch in some capacity or context.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbc62e88190b9757dc7c52d7fee |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.