Triple
T9733256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraw Regatta Festival |
E235995
|
entity |
| Predicate | sailDesign |
P90708
|
FINISHED |
| Object | hand-painted artworks |
—
|
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: hand-painted artworks | Statement: [Paraw Regatta Festival, sailDesign, hand-painted artworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sailDesign Context triple: [Paraw Regatta Festival, sailDesign, hand-painted artworks]
-
A.
sailArea
Indicates the total surface area of a vessel’s sails used to catch wind for propulsion.
-
B.
sailPlan
Indicates a plan or arrangement for how a vessel will be sailed, including intended route, timing, and sailing configuration.
-
C.
sailingClass
Indicates that one entity is a type or category of sailing activity, vessel, or competition class to which the other entity belongs or is associated.
-
D.
hasSailType
Indicates that an entity is characterized by or equipped with a specific type of sail.
-
E.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
- F. None of above. chosen
Provenance (4 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb54fe481908b0202f104b75dc1 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:22 p.m.