Triple
T11674016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushinagar |
E277445
|
entity |
| Predicate | recliningBuddhaMaterial |
P63956
|
FINISHED |
| Object | monolithic red sandstone |
—
|
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: monolithic red sandstone | Statement: [Kushinagar, recliningBuddhaMaterial, monolithic red sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recliningBuddhaMaterial Context triple: [Kushinagar, recliningBuddhaMaterial, monolithic red sandstone]
-
A.
hasSeatMaterial
Indicates that an entity’s seat is made of, or covered with, a specified material.
-
B.
statueMaterialDetail
chosen
Indicates that a statue is made of, or incorporates, a specific material with detailed characterization (e.g., type, composition, or quality).
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
hasBackrestType
Indicates the specific kind or style of backrest that an object (typically a seat or chair) possesses.
-
E.
viewOnBuddha
Indicates that an entity holds a particular perspective, opinion, or interpretive stance regarding Buddha.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.