Triple
T19784532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahanaim |
E475224
|
entity |
| Predicate | biblicalPeriod |
P9594
|
FINISHED |
| Object | Iron Age Levant |
—
|
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: Iron Age Levant | Statement: [Mahanaim, biblicalPeriod, Iron Age Levant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalPeriod Context triple: [Mahanaim, biblicalPeriod, Iron Age Levant]
-
A.
functionInBiblicalPeriod
Indicates that an entity held or performed a particular role, office, or function during a specified biblical historical period.
-
B.
culturalPeriod
chosen
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
C.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
D.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
E.
associatedBiblicalEvent
Indicates that there is a connection or linkage between an entity and a specific event described in the Bible.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.