Triple
T7018154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maldivians |
E162746
|
entity |
| Predicate | oceanicCulture |
P1968
|
FINISHED |
| Object | maritime |
—
|
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 | Statement: [Maldivians, oceanicCulture, maritime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanicCulture Context triple: [Maldivians, oceanicCulture, maritime]
-
A.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
B.
countryOfCult
Indicates that a particular cult, religious group, or worship practice is associated with, originates from, or is primarily practiced in a specific country.
-
C.
culturalKnowledge
Indicates that one entity possesses or conveys understanding of the customs, practices, values, or traditions associated with a particular culture.
-
D.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
E.
culturalRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.