Triple
T158688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabbalah |
E3232
|
entity |
| Predicate | historicalPhase |
P4711
|
FINISHED |
| Object | early mystical traditions (Heikhalot and Merkavah) |
—
|
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: early mystical traditions (Heikhalot and Merkavah) | Statement: [Kabbalah, historicalPhase, early mystical traditions (Heikhalot and Merkavah)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPhase Context triple: [Kabbalah, historicalPhase, early mystical traditions (Heikhalot and Merkavah)]
-
A.
historicalState
chosen
Indicates that an entity existed in a particular state or condition during a specified time in the past.
-
B.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
C.
historicalOutcome
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.