Triple
T2198224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossing Mandelbaum Gate: Coming of Age Between the Arabs and Israelis, 1956–1978 |
E50425
|
entity |
| Predicate | periodCoveredEnd |
P34836
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [Crossing Mandelbaum Gate: Coming of Age Between the Arabs and Israelis, 1956–1978, periodCoveredEnd, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodCoveredEnd Context triple: [Crossing Mandelbaum Gate: Coming of Age Between the Arabs and Israelis, 1956–1978, periodCoveredEnd, 1978]
-
A.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
D.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
-
E.
associatedPeriodEnd
chosen
Indicates the ending point or final date of the time period with which something is associated.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf7b65cc8190bcc5a5c52b90f33b |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.