Triple
T17286461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 420 dinghy |
E419666
|
entity |
| Predicate | hasOneDesignRules |
P6249
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [420 dinghy, hasOneDesignRules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOneDesignRules Context triple: [420 dinghy, hasOneDesignRules, yes]
-
A.
designedUnderRuleOf
Indicates that something was designed or created while a particular authority, regime, or set of rules was in power or in effect.
-
B.
coRuleOrAssociation
Indicates a relationship where two or more entities jointly hold ruling authority or share an official association in governance or leadership.
-
C.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
D.
belongsToStyle
Indicates that something is associated with, classified under, or part of a particular style or stylistic category.
-
E.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.