Triple
T19606737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taba Border Crossing |
E470624
|
entity |
| Predicate | nearResortArea |
P42027
|
FINISHED |
| Object | Eilat resort area |
—
|
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: Eilat resort area | Statement: [Taba Border Crossing, nearResortArea, Eilat resort area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearResortArea Context triple: [Taba Border Crossing, nearResortArea, Eilat resort area]
-
A.
nearbyResortArea
chosen
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
B.
nearbyResortSection
Indicates that one resort section is located close to another resort section in physical proximity.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
nearRetailPark
Indicates that one entity is located close to or in the immediate vicinity of a retail park.
-
E.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640c7ed24819091502fe0d5e139bc |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.