Triple
T4834383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heemskerck |
E108020
|
entity |
| Predicate | navigationRoute |
P24772
|
FINISHED |
| Object | from Batavia into the South Pacific |
—
|
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: from Batavia into the South Pacific | Statement: [Heemskerck, navigationRoute, from Batavia into the South Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationRoute Context triple: [Heemskerck, navigationRoute, from Batavia into the South Pacific]
-
A.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
B.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
C.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
D.
routeBetween
chosen
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
E.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.