Triple
T28991326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rich Energy |
E736031
|
entity |
| Predicate | lostLegalCaseTo |
P13508
|
FINISHED |
| Object | Whyte Bikes |
—
|
NE NERFINISHED |
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: Whyte Bikes | Statement: [Rich Energy, lostLegalCaseTo, Whyte Bikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostLegalCaseTo Context triple: [Rich Energy, lostLegalCaseTo, Whyte Bikes]
-
A.
lostClaimTo
Indicates that one entity previously held a right or ownership over something but no longer retains that claim, often due to transfer, forfeiture, or invalidation.
-
B.
loserStatus
chosen
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
C.
lostRightsBy
Indicates that one entity has had certain rights removed, revoked, or forfeited as a result of actions or circumstances involving another entity.
-
D.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
E.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7d3b5c8190937aaddff2879989 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:25 a.m.