Triple
T8128942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Albert Challenge Cup |
E189806
|
entity |
| Predicate | boatClassCode |
P24983
|
FINISHED |
| Object | M+4 (men's coxed four) |
—
|
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: M+4 (men's coxed four) | Statement: [Prince Albert Challenge Cup, boatClassCode, M+4 (men's coxed four)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatClassCode Context triple: [Prince Albert Challenge Cup, boatClassCode, M+4 (men's coxed four)]
-
A.
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.
-
B.
craftType
chosen
Indicates the specific kind or category of craft or vessel associated with an entity.
-
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.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
E.
hasSailType
Indicates that an entity is characterized by or equipped with a specific type of sail.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.