Triple
T9662641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachish |
E233624
|
entity |
| Predicate | importanceInJudah |
P1887
|
FINISHED |
| Object | second in importance after Jerusalem |
—
|
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: second in importance after Jerusalem | Statement: [Lachish, importanceInJudah, second in importance after Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInJudah Context triple: [Lachish, importanceInJudah, second in importance after Jerusalem]
-
A.
judgedIsraelFor
Indicates that an agent rendered a negative evaluation or punishment upon Israel in response to its actions or behavior.
-
B.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
C.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
D.
dramaticImportance
Indicates that one entity holds significant narrative or emotional weight or impact in relation to another within a dramatic or storytelling context.
-
E.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.