Triple
T21655035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjediva Island |
E534437
|
entity |
| Predicate | nearSeaRoute |
P62174
|
FINISHED |
| Object | Arabian Sea trade routes |
—
|
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: Arabian Sea trade routes | Statement: [Anjediva Island, nearSeaRoute, Arabian Sea trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearSeaRoute Context triple: [Anjediva Island, nearSeaRoute, Arabian Sea trade routes]
-
A.
associatedWithSeaRoute
chosen
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
B.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
C.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
D.
nearbyStrait
Indicates that one entity is located close to or adjacent to a particular strait.
-
E.
seaRouteOpened
Indicates that a maritime route between locations has been established and made available for use.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59176b28819092384fc5f8968022 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.