Triple
T36220107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vimaladharmasuriya I |
E1047821
|
entity |
| Predicate | broughtToCapital |
P184780
|
FINISHED |
| Object | Sacred Tooth Relic of the Buddha |
—
|
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: Sacred Tooth Relic of the Buddha | Statement: [Vimaladharmasuriya I, broughtToCapital, Sacred Tooth Relic of the Buddha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtToCapital Context triple: [Vimaladharmasuriya I, broughtToCapital, Sacred Tooth Relic of the Buddha]
-
A.
servedAsCapitalDuring
Indicates that a place functioned as the official capital of a political entity during a specified time period.
-
B.
passesThroughCapital
Indicates that a route, path, or trajectory goes through or intersects the capital city of a given region or country.
-
C.
appliesToCapitalOf
Indicates that a condition, rule, or characteristic is directed toward or relevant specifically to the capital city of a given entity.
-
D.
succeededAsCapitalBy
Indicates that one capital city has been replaced by another as the official capital of a political entity.
-
E.
basedInCapital
Indicates that an entity is located or has its main base of operations in a capital city.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.