Triple
T5725660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustus II the Strong |
E126257
|
entity |
| Predicate | reignRestart |
P66107
|
FINISHED |
| Object | 1709-07-08 |
—
|
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: 1709-07-08 | Statement: [Augustus II the Strong, reignRestart, 1709-07-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignRestart Context triple: [Augustus II the Strong, reignRestart, 1709-07-08]
-
A.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
C.
reignClaimStart
Indicates the point in time when a person’s asserted or contested rule or reign is claimed to have begun.
-
D.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
E.
regainsThroneFrom
Indicates that one entity takes back control of a throne or rulership position that had been held by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:47 p.m.