Triple
T18867600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land of Punt |
E461479
|
entity |
| Predicate | hadMaritimeConnectionsWith |
P27556
|
FINISHED |
| Object | Red Sea 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: Red Sea routes | Statement: [Land of Punt, hadMaritimeConnectionsWith, Red Sea routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMaritimeConnectionsWith Context triple: [Land of Punt, hadMaritimeConnectionsWith, Red Sea routes]
-
A.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
B.
hasSeaRouteConnection
chosen
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
D.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
E.
maritimeExpansion
Indicates the process by which an entity extends its influence, activities, or control over new maritime areas, routes, or territories.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.