Triple
T17817783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prasat Kravan |
E444890
|
entity |
| Predicate | hasMaterialDetail |
P1845
|
FINISHED |
| Object | carved brick bonded with vegetal mortar |
—
|
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: carved brick bonded with vegetal mortar | Statement: [Prasat Kravan, hasMaterialDetail, carved brick bonded with vegetal mortar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialDetail Context triple: [Prasat Kravan, hasMaterialDetail, carved brick bonded with vegetal mortar]
-
A.
hasMaterialType
chosen
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
B.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
-
C.
hasMaterialResource
Indicates that an entity possesses, controls, or has access to a tangible material resource.
-
D.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
E.
hasPremiumMaterials
Indicates that something is made from or includes higher-quality or superior-grade materials compared to standard options.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48880457c81908214741d6cd7a1ee |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.