Triple
T4180998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Team USA |
E88192
|
entity |
| Predicate | sailingDiscipline |
P54266
|
FINISHED |
| Object | match racing |
—
|
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: match racing | Statement: [Oracle Team USA, sailingDiscipline, match racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sailingDiscipline Context triple: [Oracle Team USA, sailingDiscipline, match racing]
-
A.
sailingNation
Indicates that a nation participates in or is represented in a sailing-related context, such as a sailing event, competition, or activity.
-
B.
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).
-
C.
sailingVenue
Indicates the location or facility where sailing activities or events take place.
-
D.
sailingTechnology
Indicates the use or involvement of specific methods, tools, or innovations related to the practice or process of sailing.
-
E.
sailArea
Indicates the total surface area of a vessel’s sails used to catch wind for propulsion.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af07059d288190a1ea79449414fbce |
completed | March 9, 2026, 5:44 p.m. |
Created at: March 9, 2026, 3:45 p.m.