Triple
T32096040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Great Sea |
E819723
|
entity |
| Predicate | hasDirectionTo |
P40218
|
FINISHED |
| Object | West leads toward Valinor |
—
|
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: West leads toward Valinor | Statement: [the Great Sea, hasDirectionTo, West leads toward Valinor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionTo Context triple: [the Great Sea, hasDirectionTo, West leads toward Valinor]
-
A.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
B.
hasDirectionFrom
Indicates that one entity has a specific orientation or directional relationship when referenced from another entity.
-
C.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
-
D.
directedTo
chosen
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
E.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 1, 2026, 12:26 a.m.