Triple
T19941995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviticus 15 |
E479327
|
entity |
| Predicate | setsBoundaryBetween |
P39423
|
FINISHED |
| Object | Holy and common |
—
|
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: Holy and common | Statement: [Leviticus 15, setsBoundaryBetween, Holy and common]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsBoundaryBetween Context triple: [Leviticus 15, setsBoundaryBetween, Holy and common]
-
A.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
B.
boundaryBetween
chosen
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
D.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
E.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6318848190a1dd3e0a6fea3fe2 |
completed | April 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.