Triple
T18760290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Buddha |
E458752
|
entity |
| Predicate | usesFoundMaterial |
P78356
|
FINISHED |
| Object | temple incense ash |
—
|
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: temple incense ash | Statement: [Ash Buddha, usesFoundMaterial, temple incense ash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFoundMaterial Context triple: [Ash Buddha, usesFoundMaterial, temple incense ash]
-
A.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
B.
materialFound
chosen
Indicates that a particular material is present, discovered, or detected in association with a specified entity or location.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
E.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d7ecca881909d6c262837b621b3 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.