Triple
T18348061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jajaghu |
E439593
|
entity |
| Predicate | hasReliefsFrom |
P131457
|
FINISHED |
| Object | Tantri stories |
—
|
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: Tantri stories | Statement: [Jajaghu, hasReliefsFrom, Tantri stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefsFrom Context triple: [Jajaghu, hasReliefsFrom, Tantri stories]
-
A.
hasReliefOf
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
B.
hasRelief
Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
-
C.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
D.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
-
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. chosen
Provenance (4 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f594f88190a683e6224e091593 |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.