Triple
T31249030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | פדן ארם |
E796763
|
entity |
| Predicate | travelDestinationOf |
P21947
|
FINISHED |
| Object | יעקב מבאר שבע לחרן |
—
|
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: יעקב מבאר שבע לחרן | Statement: [פדן ארם, travelDestinationOf, יעקב מבאר שבע לחרן]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelDestinationOf Context triple: [פדן ארם, travelDestinationOf, יעקב מבאר שבע לחרן]
-
A.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
travelScope
Indicates the extent or range within which travel is allowed, intended, or applicable for an entity or activity.
-
C.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
D.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
E.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 9:11 p.m.