Triple
T9844515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Qurbana |
E239304
|
entity |
| Predicate | requiresElements |
P3097
|
FINISHED |
| Object | bread |
—
|
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: bread | Statement: [Holy Qurbana, requiresElements, bread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresElements Context triple: [Holy Qurbana, requiresElements, bread]
-
A.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
B.
requiredDesignElement
Indicates that one entity must include, use, or incorporate another entity as a necessary design component or feature.
-
C.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
D.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
-
E.
requiresPresence
Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35dc29c819080203be5b904dc9d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.