Triple
T19966216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laos and Cambodia |
E479939
|
entity |
| Predicate | shareArtisticTradition |
P8153
|
FINISHED |
| Object | Buddhist sculpture |
—
|
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: Buddhist sculpture | Statement: [Laos and Cambodia, shareArtisticTradition, Buddhist sculpture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareArtisticTradition Context triple: [Laos and Cambodia, shareArtisticTradition, Buddhist sculpture]
-
A.
traditionalArtForm
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
-
B.
sharesArtMovementWith
Indicates that two entities are associated with or belong to the same artistic movement or style.
-
C.
intangibleHeritageDomain
Indicates that something belongs to, or is categorized within, a specific domain or category of intangible cultural heritage.
-
D.
paintingTradition
Indicates a stylistic or cultural school of painting to which an artwork or artist belongs.
-
E.
sharesDesignTraditionWith
chosen
Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc4f47c8190a721f5e488150d81 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.