Triple
T22141210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windermere Cup |
E547161
|
entity |
| Predicate | typicalBoatClass |
P109622
|
FINISHED |
| Object | eight-oared shells |
—
|
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: eight-oared shells | Statement: [Windermere Cup, typicalBoatClass, eight-oared shells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBoatClass Context triple: [Windermere Cup, typicalBoatClass, eight-oared shells]
-
A.
notableBoatClass
Indicates that the subject is a notable or significant example of the specified class or type of boat.
-
B.
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.
-
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.
hasTraditionalBoatType
Indicates that an entity is associated with or characterized by a specific traditional type of boat.
-
E.
typicalShipTypes
chosen
Indicates that the subject is commonly or characteristically associated with the specified types or categories of ships.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129beb6c8819083be3b7479bc032f |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.