Triple
T22320880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigak people |
E551780
|
entity |
| Predicate | boatTechnology |
P81629
|
FINISHED |
| Object | outrigger canoes |
—
|
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: outrigger canoes | Statement: [Tigak people, boatTechnology, outrigger canoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatTechnology Context triple: [Tigak people, boatTechnology, outrigger canoes]
-
A.
boatPower
Indicates a relationship where a boat is characterized by or associated with a specific power rating or propulsion strength.
-
B.
sailingTechnology
Indicates the use or involvement of specific methods, tools, or innovations related to the practice or process of sailing.
-
C.
boatConfiguration
chosen
Indicates the specific arrangement, layout, or setup of components or features on a boat.
-
D.
marineResources
Indicates a relationship where one entity possesses, provides, or is associated with marine-based resources (such as fish, minerals, or other ocean-derived materials) used or managed by another entity.
-
E.
boatStudio
Indicates a relationship where a boat is associated with, produced by, or represented by a particular studio or production company.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15764d3a48190af79ce4642b7f563 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.