Triple
T20593689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göbekli Tepe |
E505994
|
entity |
| Predicate | hasReliefDepiction |
P11199
|
FINISHED |
| Object | wild animals |
—
|
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: wild animals | Statement: [Göbekli Tepe, hasReliefDepiction, wild animals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefDepiction Context triple: [Göbekli Tepe, hasReliefDepiction, wild animals]
-
A.
hasReliefFeature
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.
hasReliefOf
chosen
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
D.
hasReliefsFrom
Indicates that one entity experiences a reduction or alleviation of symptoms, problems, or burdens as a result of another entity.
-
E.
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.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a97e3a7c8190b0b4604aaf40564b |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.