Triple
T11264630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Jerusalem |
E266650
|
entity |
| Predicate | priorTo |
P97
|
FINISHED |
| Object | 1967 Six-Day War division of 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: 1967 Six-Day War division of Jerusalem | Statement: [West Jerusalem, priorTo, 1967 Six-Day War division of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priorTo Context triple: [West Jerusalem, priorTo, 1967 Six-Day War division of Jerusalem]
-
A.
grandPrior
Indicates that one entity is the grandparent (parent of a parent) of another entity in a hierarchical or genealogical structure.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
D.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
E.
prioritises
Indicates that one entity gives greater importance, preference, or precedence to another entity or task over alternatives.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94d56048190bf808e1bc2188714 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.