Triple
T17300110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alinghi |
E420017
|
entity |
| Predicate | 2010America’sCupResult |
P126892
|
FINISHED |
| Object | lost match |
—
|
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: lost match | Statement: [Alinghi, 2010America’sCupResult, lost match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2010America’sCupResult Context triple: [Alinghi, 2010America’sCupResult, lost match]
-
A.
sailingDiscipline
Indicates a specific category or type of sailing activity or competition in which an entity participates or is involved.
-
B.
sailingSeries
Indicates a relationship where multiple sailing events or races are grouped together as part of the same organized series or competition.
-
C.
someSkipperedBy
Indicates that a vessel or boat is commanded or captained by a particular person serving as its skipper.
-
D.
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.
-
E.
sailingNation
Indicates that a nation participates in or is represented in a sailing-related context, such as a sailing event, competition, or activity.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f9e5ac8190ba0b5820790112d9 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:41 a.m.