Triple
T15087617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Spitsbergen Current |
E360319
|
entity |
| Predicate | transportsProperty |
P117256
|
FINISHED |
| Object | heat |
—
|
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: heat | Statement: [West Spitsbergen Current, transportsProperty, heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportsProperty Context triple: [West Spitsbergen Current, transportsProperty, heat]
-
A.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
B.
hasTransportationElement
Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
-
C.
hasTransportationRelation
Indicates a relationship in which one entity provides, uses, is connected by, or is otherwise associated with a means or mode of transportation to another entity or location.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
- F. None of above. chosen
Provenance (4 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:03 a.m.