Triple
T29725318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chagigah (festival peace offering) |
E752162
|
entity |
| Predicate | historicalPeriodOfPractice |
P9816
|
FINISHED |
| Object | First Temple period |
—
|
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: First Temple period | Statement: [Chagigah (festival peace offering), historicalPeriodOfPractice, First Temple period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfPractice Context triple: [Chagigah (festival peace offering), historicalPeriodOfPractice, First Temple period]
-
A.
historicalPractice
chosen
Indicates that an action, behavior, or relationship occurred as a customary or established practice during a past historical period.
-
B.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
C.
periodOfPractice
Indicates the span of time during which an activity, role, or practice is carried out.
-
D.
inceptionOfPractice
Indicates the point or event at which a particular practice, activity, or custom begins or is first established.
-
E.
historicalPeriodOfTesting
Indicates the time period or era during which the testing activity or process took place.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: April 28, 2026, 7:38 p.m.