Triple
T11665976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindavi Swarajya as a formal kingdom |
E277246
|
entity |
| Predicate | coronationOfFounder |
P4006
|
FINISHED |
| Object | 1674 |
—
|
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: 1674 | Statement: [Hindavi Swarajya as a formal kingdom, coronationOfFounder, 1674]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationOfFounder Context triple: [Hindavi Swarajya as a formal kingdom, coronationOfFounder, 1674]
-
A.
firstCoronationHeldFor
Indicates that a particular entity was the subject or beneficiary of the first coronation event associated with another entity.
-
B.
crownedAs
Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
-
C.
firstCoronationHeld
chosen
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
D.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a43f438081909da476294a057c38 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.