Triple
T9504314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulekites |
E229223
|
entity |
| Predicate | timeOfDeparture |
P14163
|
FINISHED |
| Object | around the destruction of Jerusalem by Babylon |
—
|
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: around the destruction of Jerusalem by Babylon | Statement: [Mulekites, timeOfDeparture, around the destruction of Jerusalem by Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDeparture Context triple: [Mulekites, timeOfDeparture, around the destruction of Jerusalem by Babylon]
-
A.
departureTime
chosen
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
B.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
C.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
D.
placeOfDeparture
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
E.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9840148081908df237f212b62e67 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.