Triple
T3844461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Jayawardenepura Kotte |
E93534
|
entity |
| Predicate | eraOfHistoricalKingdom |
P51877
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Sri Jayawardenepura Kotte, eraOfHistoricalKingdom, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfHistoricalKingdom Context triple: [Sri Jayawardenepura Kotte, eraOfHistoricalKingdom, 15th century]
-
A.
foundedKingdom
Indicates that an entity established or created a kingdom as its founder.
-
B.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
C.
kingdomAssociatedWith
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
D.
countryRuled
Indicates that one entity exercises governing authority or political control over a country.
-
E.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb655c081909ec5ff3d09eb4778 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:18 p.m.