Triple
T20689870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indies |
E508519
|
entity |
| Predicate | tradeRouteType |
P62174
|
FINISHED |
| Object | maritime trade route |
—
|
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: maritime trade route | Statement: [Indies, tradeRouteType, maritime trade route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeRouteType Context triple: [Indies, tradeRouteType, maritime trade route]
-
A.
includesTradeRoute
Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
-
B.
tradRoutes
Indicates a relationship where one location serves as a trade route to or from another location, facilitating the movement of goods or commerce between them.
-
C.
tradeDestination
Indicates the location or entity to which goods, services, or financial assets are sent or directed as part of a trade transaction.
-
D.
associatedWithSeaRoute
chosen
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
E.
connectsInlandRoutesTo
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10cb5588190acb88f2c82fc593a |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:08 p.m.