Triple
T30617797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 27 |
E779360
|
entity |
| Predicate | givesInstructionsFor |
P18444
|
FINISHED |
| Object | altar of burnt offering |
—
|
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: altar of burnt offering | Statement: [Exodus 27, givesInstructionsFor, altar of burnt offering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesInstructionsFor Context triple: [Exodus 27, givesInstructionsFor, altar of burnt offering]
-
A.
usageInstruction
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle another entity.
-
B.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to another entity.
-
C.
canInstruct
Indicates that one entity has the authority or ability to give instructions or guidance to another entity.
-
D.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
E.
instruction
Indicates that one entity provides a directive or order specifying an action that another entity should perform.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689eca0348190a4f8e54e0a56f797 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.