Triple
T26830808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford reserve crews |
E675493
|
entity |
| Predicate | hasBlueBoatRelationship |
P161523
|
FINISHED |
| Object | secondary to the Oxford Blue Boat |
—
|
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: secondary to the Oxford Blue Boat | Statement: [Oxford reserve crews, hasBlueBoatRelationship, secondary to the Oxford Blue Boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlueBoatRelationship Context triple: [Oxford reserve crews, hasBlueBoatRelationship, secondary to the Oxford Blue Boat]
-
A.
hasBoat
Indicates that one entity possesses, owns, or has control over a boat.
-
B.
hasBoatLine
Indicates that one entity operates, owns, or is associated with a particular boat service or boat route line.
-
C.
boatTraveledOn
Indicates that a boat moved or was transported along or across a specified body of water or route.
-
D.
hasSail
Indicates that one entity possesses or is equipped with a sail used for catching wind.
-
E.
hasSailType
Indicates that an entity is characterized by or equipped with a specific type of sail.
- F. None of above. chosen
Provenance (4 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61adc60c88190924d7b71d52851e8 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 5:01 a.m.