Triple
T5395940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarshish |
E120653
|
entity |
| Predicate | perceivedDirection |
P59277
|
FINISHED |
| Object | westward from the Levant |
—
|
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: westward from the Levant | Statement: [Tarshish, perceivedDirection, westward from the Levant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedDirection Context triple: [Tarshish, perceivedDirection, westward from the Levant]
-
A.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
B.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
C.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
D.
directionOfAppearance
chosen
Indicates the spatial direction or orientation from which something becomes visible or appears relative to a reference point or observer.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.