Triple
T25265215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 1947 |
E633411
|
entity |
| Predicate | interceptionDate |
P154140
|
FINISHED |
| Object | 1947-07-18 |
—
|
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: 1947-07-18 | Statement: [Exodus 1947, interceptionDate, 1947-07-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interceptionDate Context triple: [Exodus 1947, interceptionDate, 1947-07-18]
-
A.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
B.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
C.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
D.
impoundmentDate
chosen
Indicates the date on which an entity (such as property, funds, or an animal) is formally taken into custody or impounded by an authority.
-
E.
attackDate
Indicates the calendar date on which an attack or assault event took place.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:14 p.m.