Triple
T34666877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Kinds |
E890280
|
entity |
| Predicate | commandedInChapter |
P36548
|
FINISHED |
| Object | Leviticus 23 |
—
|
NE NERFINISHED |
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: Leviticus 23 | Statement: [Four Kinds, commandedInChapter, Leviticus 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedInChapter Context triple: [Four Kinds, commandedInChapter, Leviticus 23]
-
A.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
B.
foundInChapter
chosen
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
C.
chapterMentioned
Indicates that a specific chapter is referenced or cited within a given context or source.
-
D.
seatOfChapter
Indicates that a location serves as the official meeting place or headquarters for a specific chapter (such as a local branch of an organization).
-
E.
basedOnChapter
Indicates that something (such as a work, section, or element) is derived from, adapted from, or primarily informed by a specific chapter.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 2:05 a.m.