Triple
T4178488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FJ dinghy |
E86534
|
entity |
| Predicate | hasSailPlan |
P23910
|
FINISHED |
| Object | mainsail and jib |
—
|
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: mainsail and jib | Statement: [FJ dinghy, hasSailPlan, mainsail and jib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSailPlan Context triple: [FJ dinghy, hasSailPlan, mainsail and jib]
-
A.
sailPlan
chosen
Indicates a plan or arrangement for how a vessel will be sailed, including intended route, timing, and sailing configuration.
-
B.
hasSailType
Indicates that an entity is characterized by or equipped with a specific type of sail.
-
C.
sailingUnder
Indicates that one entity (typically a vessel) is operating or traveling while registered, flagged, or officially recognized under the authority or jurisdiction of another entity (such as a country or organization).
-
D.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
-
E.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.