Triple
T26289046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantar people |
E661216
|
entity |
| Predicate | usesMaritimeTechnology |
P4959
|
FINISHED |
| Object | wooden boats |
—
|
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: wooden boats | Statement: [Pantar people, usesMaritimeTechnology, wooden boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMaritimeTechnology Context triple: [Pantar people, usesMaritimeTechnology, wooden boats]
-
A.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
B.
usesAtSea
chosen
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
C.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
D.
sailingTechnology
Indicates the use or involvement of specific methods, tools, or innovations related to the practice or process of sailing.
-
E.
navalTechnologySignificance
Indicates the importance or impact that a particular naval technology has within a given historical, strategic, or operational context.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 10:07 p.m.