Triple
T3222580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unangan |
E67542
|
entity |
| Predicate | traditionalWatercraftType |
P22942
|
FINISHED |
| Object | baidarka |
—
|
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: baidarka | Statement: [Unangan, traditionalWatercraftType, baidarka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalWatercraftType Context triple: [Unangan, traditionalWatercraftType, baidarka]
-
A.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
B.
traditionalVessel
chosen
Indicates that one entity is a vessel or container that follows traditional, customary, or historically established forms, designs, or uses in relation to another entity.
-
C.
craftType
Indicates the specific kind or category of craft or vessel associated with an entity.
-
D.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
E.
hasBoat
Indicates that one entity possesses, owns, or has control over a boat.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae196da8819086fdcf5d2b21a702 |
completed | March 8, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.