Triple
T4767915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zechariah |
E105856
|
entity |
| Predicate | performedDuty |
P2297
|
FINISHED |
| Object | burning incense in the Temple sanctuary |
—
|
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: burning incense in the Temple sanctuary | Statement: [Zechariah, performedDuty, burning incense in the Temple sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedDuty Context triple: [Zechariah, performedDuty, burning incense in the Temple sanctuary]
-
A.
performed
chosen
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
B.
dutyRecognized
Indicates that an obligation or responsibility has been acknowledged or accepted by the relevant party.
-
C.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
D.
hasDutyStatus
Indicates that an entity currently holds a particular duty or operational status in relation to a role, task, or assignment.
-
E.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.