Triple
T30883437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapun people |
E786686
|
entity |
| Predicate | hasMaritimeTraditions |
P20564
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mapun people, hasMaritimeTraditions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeTraditions Context triple: [Mapun people, hasMaritimeTraditions, true]
-
A.
hasMaritimeHeritage
chosen
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
B.
hasNavalTradition
Indicates that an entity possesses a history, culture, or established practice of maritime or naval activities.
-
C.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
D.
seaNavigationTradition
Indicates a tradition, practice, or custom related to navigating or traveling by sea.
-
E.
hasSeafaringTheme
Indicates that something is characterized by or prominently features elements related to seafaring, such as ships, sailors, or maritime life.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
Created at: April 29, 2026, 8:48 p.m.