Triple
T15104215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Ruthenia |
E360745
|
entity |
| Predicate | coronationOfFirstMonarch |
P44069
|
FINISHED |
| Object | 1253 |
—
|
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: 1253 | Statement: [King of Ruthenia, coronationOfFirstMonarch, 1253]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationOfFirstMonarch Context triple: [King of Ruthenia, coronationOfFirstMonarch, 1253]
-
A.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
B.
firstCoronationHeldFor
chosen
Indicates that a particular entity was the subject or beneficiary of the first coronation event associated with another entity.
-
C.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
D.
coronationEvent
Indicates the event in which a person is formally invested with royal authority and crowned as a monarch.
-
E.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00551521c8190b48d1a074bb4bdfc |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.