Triple
T22583117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian obelisk |
E544615
|
entity |
| Predicate | hasSurfaceDecoration |
P38145
|
FINISHED |
| Object | vertical hieroglyphic inscriptions |
—
|
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: vertical hieroglyphic inscriptions | Statement: [Egyptian obelisk, hasSurfaceDecoration, vertical hieroglyphic inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceDecoration Context triple: [Egyptian obelisk, hasSurfaceDecoration, vertical hieroglyphic inscriptions]
-
A.
hasDecor
chosen
Indicates that one entity possesses, features, or is adorned with a particular decorative element or style.
-
B.
containsDecorationFrom
Indicates that one entity includes or incorporates a decorative element that originates from another entity.
-
C.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
D.
hasSurfaceComposition
Indicates that one entity has a surface made up of, or characterized by, the material or composition specified by another entity.
-
E.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15ff26d6481908cc058f8c4b87e75 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.