Triple
T25265213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 1947 |
E633411
|
entity |
| Predicate | intendedLandingArea |
P90110
|
FINISHED |
| Object | coast of Palestine near Tel Aviv |
—
|
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: coast of Palestine near Tel Aviv | Statement: [Exodus 1947, intendedLandingArea, coast of Palestine near Tel Aviv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedLandingArea Context triple: [Exodus 1947, intendedLandingArea, coast of Palestine near Tel Aviv]
-
A.
intendedLandingRegion
chosen
Indicates the geographic area or region where something is planned or expected to land.
-
B.
partOfLandingSector
Indicates that one entity constitutes a component or subdivision within a larger landing sector.
-
C.
landedNear
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
-
D.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
E.
lastFlightPlannedLandingSite
Indicates the location where the most recent flight is scheduled to land.
- 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_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:14 p.m.