Triple
T17823852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angkor Thom |
E445059
|
entity |
| Predicate | builtInMaterial |
P1272
|
FINISHED |
| Object | 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: sandstone | Statement: [Angkor Thom, builtInMaterial, sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtInMaterial Context triple: [Angkor Thom, builtInMaterial, sandstone]
-
A.
exampleMaterial
Indicates that something serves as a representative or illustrative material or sample of something else.
-
B.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
C.
featuresMaterialType
Indicates that an entity is characterized by or incorporates a specific type of material.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
builtIn
Indicates that one entity is inherently included as a standard, pre-existing component or feature of another entity, rather than being added or installed separately.
- 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_69e4891352ac8190ad3d669fea1c9fbb |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:15 a.m.