Triple
T11639476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Turn |
E276621
|
entity |
| Predicate | routeEnvironment |
P85507
|
FINISHED |
| Object | remote wilderness |
—
|
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: remote wilderness | Statement: [Hurricane Turn, routeEnvironment, remote wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeEnvironment Context triple: [Hurricane Turn, routeEnvironment, remote wilderness]
-
A.
navigationEnvironment
chosen
Indicates the contextual conditions or surroundings in which navigation or movement from one place to another occurs.
-
B.
transmissionEnvironment
Indicates the medium or setting through which something (such as information, energy, or a signal) is transmitted from one entity to another.
-
C.
routeSystem
Indicates a transportation or communication network framework within which specific routes are organized, defined, or managed.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
routeOrigin
Indicates the starting point or source location from which a route begins.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.