Triple
T6500978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shishak king of Egypt |
E148886
|
entity |
| Predicate | tookFromJerusalem |
P71233
|
FINISHED |
| Object | treasures of the Temple of the LORD |
—
|
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: treasures of the Temple of the LORD | Statement: [Shishak king of Egypt, tookFromJerusalem, treasures of the Temple of the LORD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookFromJerusalem Context triple: [Shishak king of Egypt, tookFromJerusalem, treasures of the Temple of the LORD]
-
A.
lostJerusalemTo
Indicates that one party surrendered control of Jerusalem to another, typically through defeat or loss in conflict.
-
B.
numberOfPilgrimagesToJerusalem
Indicates the count of times an entity has undertaken pilgrimages to Jerusalem.
-
C.
cameUnderIsraeliControl
Indicates that one entity transitioned to being governed, occupied, or administered by Israeli authorities.
-
D.
reignAsKingOfJerusalemEnd
Indicates the point in time or event at which an individual’s reign as king of Jerusalem comes to an end.
-
E.
lostJerusalemYear
Indicates the specific year in which the referenced party lost control of Jerusalem.
- F. None of above. chosen
Provenance (4 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:42 p.m.