Triple
T31310458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fridtjof Nansen's Greenland expedition of 1888 |
E798448
|
entity |
| Predicate | directionOfCrossing |
P51219
|
FINISHED |
| Object | east-to-west |
—
|
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: east-to-west | Statement: [Fridtjof Nansen's Greenland expedition of 1888, directionOfCrossing, east-to-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfCrossing Context triple: [Fridtjof Nansen's Greenland expedition of 1888, directionOfCrossing, east-to-west]
-
A.
crossingDirection
chosen
Indicates the direction in which one entity moves or passes across another reference point, boundary, or path.
-
B.
directionFromCharingCross
Indicates the compass direction of one place or object as measured from Charing Cross.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
E.
orientationOfCross
Indicates the spatial orientation or alignment of a cross relative to a reference frame or object.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 9:15 p.m.