Triple
T35590269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruhuna region |
E1028478
|
entity |
| Predicate | wasKingdomDuring |
P28270
|
FINISHED |
| Object | Anuradhapura period |
—
|
NE NERFINISHED |
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: Anuradhapura period | Statement: [Ruhuna region, wasKingdomDuring, Anuradhapura period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKingdomDuring Context triple: [Ruhuna region, wasKingdomDuring, Anuradhapura period]
-
A.
wasKingDuring
Indicates that one entity held the position or title of king throughout the time period associated with another entity.
-
B.
wasKingdomUntil
Indicates that an entity functioned as a kingdom governing another entity up to a specified end time or event.
-
C.
wasClientKingdomUntil
Indicates that an entity functioned as a client kingdom subordinate to another entity up until a specified end date or time.
-
D.
wasKingdom
chosen
Indicates that one entity functioned as the sovereign kingdom or ruling polity of another entity during a particular period.
-
E.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.