Triple
T17299865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW Oracle Racing |
E420012
|
entity |
| Predicate | roleIn2010America'sCup |
P74512
|
FINISHED |
| Object | challenger |
—
|
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: challenger | Statement: [BMW Oracle Racing, roleIn2010America'sCup, challenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleIn2010America'sCup Context triple: [BMW Oracle Racing, roleIn2010America'sCup, challenger]
-
A.
boatRaceRole
chosen
Indicates the specific role or function an entity has within the context of a boat race (e.g., participant, organizer, official).
-
B.
sailingDiscipline
Indicates a specific category or type of sailing activity or competition in which an entity participates or is involved.
-
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.
RyderCupRole
Indicates that an entity holds a specific role or position in relation to the Ryder Cup event.
- 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_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. |
Created at: April 10, 2026, 5:41 a.m.