Triple
T37318104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Qastal |
E926393
|
entity |
| Predicate | nearbyLocalityAfter1948 |
P198981
|
FINISHED |
| Object | Mevaseret Zion |
—
|
NE NERFINISHED |
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: Mevaseret Zion | Statement: [al-Qastal, nearbyLocalityAfter1948, Mevaseret Zion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyLocalityAfter1948 Context triple: [al-Qastal, nearbyLocalityAfter1948, Mevaseret Zion]
-
A.
nearbyLocalityWestBank
Indicates that one locality is geographically near another locality located in the West Bank region.
-
B.
nearbyIsraeliSettlement
Indicates that one entity is located close in distance to an Israeli settlement.
-
C.
hasNearbyArabLocality
Indicates that one entity has an Arab locality situated in close geographic proximity to it.
-
D.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
E.
nearbySettlementGR
Indicates that one settlement is geographically located close to another settlement.
- F. None of above. chosen
Provenance (4 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
| PDg | Predicate description generation | batch_69ff17bda59c8190b27c524f3e01c6df |
completed | May 9, 2026, 11:17 a.m. |
Created at: May 3, 2026, 4:16 p.m.