Triple
T31797391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Zionism, 1600–1918 |
E811633
|
entity |
| Predicate | chronologicallyBeginsWith |
P76219
|
FINISHED |
| Object | early modern period |
—
|
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 modern period | Statement: [History of Zionism, 1600–1918, chronologicallyBeginsWith, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyBeginsWith Context triple: [History of Zionism, 1600–1918, chronologicallyBeginsWith, early modern period]
-
A.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
B.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
chronologyPrecedes
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
E.
chronologyStart
chosen
Indicates the point in time at which a sequence, event, or temporal record begins.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 30, 2026, 11:41 p.m.