Triple
T22886798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatadage at Polonnaruwa |
E567623
|
entity |
| Predicate | moonstonesDepict |
P150132
|
FINISHED |
| Object | concentric bands of animals and floral motifs |
—
|
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: concentric bands of animals and floral motifs | Statement: [Vatadage at Polonnaruwa, moonstonesDepict, concentric bands of animals and floral motifs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moonstonesDepict Context triple: [Vatadage at Polonnaruwa, moonstonesDepict, concentric bands of animals and floral motifs]
-
A.
moonSymbolizes
Indicates that the moon serves as a symbol or representation of a particular idea, quality, or concept.
-
B.
viewOnMeteorites
Indicates a stance, opinion, or perspective that an entity holds regarding meteorites.
-
C.
moonNamingTheme
Indicates that one entity serves as the thematic basis or inspiration for how another entity’s moons are named.
-
D.
viewOnMoon
Indicates that an entity has a visual perspective or observable view from the surface or vicinity of the Moon.
-
E.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc1e3408190833a062afbea509d |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:40 p.m.