Triple
T20938791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha Motor Racing |
E515657
|
entity |
| Predicate | hasTeamStatus |
P11651
|
FINISHED |
| Object | official Yamaha works team |
—
|
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: official Yamaha works team | Statement: [Yamaha Motor Racing, hasTeamStatus, official Yamaha works team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamStatus Context triple: [Yamaha Motor Racing, hasTeamStatus, official Yamaha works team]
-
A.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
B.
hasCurrentTeam
Indicates that an entity is presently a member of or affiliated with a specific team.
-
C.
teamState
chosen
Indicates the current status or condition of a team within a given context or process.
-
D.
hasTeamInGame
Indicates that a particular game involves or includes a specific team as a participant.
-
E.
universityTeamStatus
Indicates the role or standing an entity holds within a university-affiliated team (e.g., member, coach, captain, or other status).
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f95419a48190b7f62abc59f38bef |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.