Triple
T23917018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Yishuv of Jerusalem |
E602109
|
entity |
| Predicate | endOfDominancePeriod |
P86114
|
FINISHED |
| Object | early 20th century |
—
|
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 20th century | Statement: [Old Yishuv of Jerusalem, endOfDominancePeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfDominancePeriod Context triple: [Old Yishuv of Jerusalem, endOfDominancePeriod, early 20th century]
-
A.
politicalDominancePeriodEnd
chosen
Indicates the point in time when an entity’s period of political dominance or control comes to an end.
-
B.
endOfExtensionPeriod
Indicates that a previously granted extension has reached or passed its final allowable time limit.
-
C.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
D.
temporalAuthorityEndedBy
Indicates that a period of temporal authority or secular power held by one entity comes to an end as a result of an action or event caused by another entity.
-
E.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce9a744c819080bd30176b8de9a0 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:40 p.m.