Triple
T25851656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loaísa expedition |
E651225
|
entity |
| Predicate | typeOfNavigation |
P34226
|
FINISHED |
| Object | oceanic voyage |
—
|
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: oceanic voyage | Statement: [Loaísa expedition, typeOfNavigation, oceanic voyage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfNavigation Context triple: [Loaísa expedition, typeOfNavigation, oceanic voyage]
-
A.
navigationType
chosen
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
B.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
C.
navigationRightType
Indicates the type or category of a right or permission related to navigation or movement in a given context.
-
D.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
E.
navigationRole
Indicates that one entity serves as a navigational aid, control, or function that helps users move through or orient themselves within another entity (such as an interface, document, or environment).
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 22, 2026, 7:58 a.m.