Triple
T18165428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | وادي عربة |
E434879
|
entity |
| Predicate | يمتد تقريباً باتجاه |
P40031
|
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: [وادي عربة, يمتد تقريباً باتجاه, شمال-جنوب]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يمتد تقريباً باتجاه Context triple: [وادي عربة, يمتد تقريباً باتجاه, شمال-جنوب]
-
A.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
approximateDirection
chosen
Indicates that one entity is located in a general or rough directional relation (e.g., roughly north, south, etc.) relative to another entity, without specifying an exact bearing.
-
D.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
E.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec71b7881908d123d0cea3adf1f |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.