Triple
T25339026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Doors |
E635355
|
entity |
| Predicate | hasReliefDepth |
P22470
|
FINISHED |
| Object | high relief |
—
|
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: high relief | Statement: [South Doors, hasReliefDepth, high relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefDepth Context triple: [South Doors, hasReliefDepth, high relief]
-
A.
hasReliefFeature
chosen
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
-
B.
hasRelief
Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
-
C.
hasReliefRange
Indicates a relationship where an entity is associated with a specified range or interval of relief (e.g., elevation difference or surface variation) values.
-
D.
hasRelativeRelief
Indicates a relationship where one entity is characterized by the degree of variation in elevation or relief relative to another reference entity or area.
-
E.
hasReliefOf
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 21, 2026, 1:32 p.m.