Triple
T33508786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf maritime trade network |
E858183
|
entity |
| Predicate | navigationReliedOn |
P10507
|
FINISHED |
| Object | monsoon winds |
—
|
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: monsoon winds | Statement: [Gulf maritime trade network, navigationReliedOn, monsoon winds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationReliedOn Context triple: [Gulf maritime trade network, navigationReliedOn, monsoon winds]
-
A.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
B.
navigatedBy
chosen
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
navigationSupport
Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
-
E.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:38 a.m.