Triple
T19071645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pihta |
E466804
|
entity |
| Predicate | hasPreparationContext |
P134186
|
FINISHED |
| Object | ritually prepared |
—
|
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: ritually prepared | Statement: [Pihta, hasPreparationContext, ritually prepared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreparationContext Context triple: [Pihta, hasPreparationContext, ritually prepared]
-
A.
isPreparedAs
Indicates that one entity is made ready, arranged, or configured in a particular way or form as specified by another entity.
-
B.
hasPreambleContext
Indicates that something is associated with or occurs within the contextual setting provided by a preamble (such as introductory or prefatory material).
-
C.
hasPlanningContext
Indicates that an entity is associated with a specific planning-related situation, scope, or set of conditions that frame how it should be interpreted or used.
-
D.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
-
E.
preparesWith
Indicates that one entity is used as a means, tool, or method by which another entity is prepared or made ready.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19fa6948190bdf8e8ec022e12f2 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.