Triple
T8239058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Mother Challenge Cup |
E192484
|
entity |
| Predicate | boatRigging |
P22490
|
FINISHED |
| Object | sculling |
—
|
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: sculling | Statement: [Queen Mother Challenge Cup, boatRigging, sculling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatRigging Context triple: [Queen Mother Challenge Cup, boatRigging, sculling]
-
A.
shipRig
Indicates that one entity is equipped with or configured using the rigging system specified by another entity.
-
B.
typeOfRigging
chosen
Indicates the kind or configuration of rigging used in relation to an object or structure.
-
C.
hasShipRig
Indicates that an entity is equipped with, or characterized by, a particular type of ship rigging configuration.
-
D.
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).
-
E.
boatStudio
Indicates a relationship where a boat is associated with, produced by, or represented by a particular studio or production company.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783a8cf48190bf85394fd3bd79e2 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.