Triple
T11845249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiri trade voyages |
E281757
|
entity |
| Predicate | navigationalEnvironment |
P85507
|
FINISHED |
| Object | open sea |
—
|
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: open sea | Statement: [Hiri trade voyages, navigationalEnvironment, open sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalEnvironment Context triple: [Hiri trade voyages, navigationalEnvironment, open sea]
-
A.
navigationEnvironment
chosen
Indicates the contextual conditions or surroundings in which navigation or movement from one place to another occurs.
-
B.
navigability
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
isNavigationalAid
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
E.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.