Triple
T16978194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarenput I |
E411867
|
entity |
| Predicate | depictedPerforming |
P125467
|
FINISHED |
| Object | offering rituals in tomb decoration |
—
|
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: offering rituals in tomb decoration | Statement: [Sarenput I, depictedPerforming, offering rituals in tomb decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictedPerforming Context triple: [Sarenput I, depictedPerforming, offering rituals in tomb decoration]
-
A.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
B.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
C.
performances
Indicates that an entity stages, presents, or executes artistic or entertainment events for an audience.
-
D.
performsSongWith
Indicates that two or more entities jointly perform or present a song together.
-
E.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d185a9408190a991bf8a1ef694f0 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:32 a.m.