Triple
T31399824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese navigators |
E800965
|
entity |
| Predicate | openedSeaRoute |
P13848
|
FINISHED |
| Object | sea route around Cape of Good Hope to India |
—
|
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: sea route around Cape of Good Hope to India | Statement: [Portuguese navigators, openedSeaRoute, sea route around Cape of Good Hope to India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedSeaRoute Context triple: [Portuguese navigators, openedSeaRoute, sea route around Cape of Good Hope to India]
-
A.
seaRouteOpened
chosen
Indicates that a maritime route between locations has been established and made available for use.
-
B.
controlledSeaRoute
Indicates that one entity has authority over, or the ability to regulate and manage access through, a particular maritime route used for navigation or transport.
-
C.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
D.
seaVoyages
Indicates that one entity undertakes or is associated with journeys or travel by sea to or involving another entity.
-
E.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 9:19 p.m.