Triple

T33841463
Position Surface form Disambiguated ID Type / Status
Subject Simon Yates E867367 entity
Predicate memberOfSportsTeam P330 FINISHED
Object Orica–GreenEDGE
Orica–GreenEDGE was an Australian professional road cycling team that competed at the UCI WorldTour level and was known for its successes in Grand Tours and one-day races.
E2070451 NE 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: Orica–GreenEDGE | Statement: [Simon Yates, memberOfSportsTeam, Orica–GreenEDGE]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Orica–GreenEDGE
Triple: [Simon Yates, memberOfSportsTeam, Orica–GreenEDGE]
Generated description
Orica–GreenEDGE was an Australian professional road cycling team that competed at the UCI WorldTour level and was known for its successes in Grand Tours and one-day races.

Provenance (5 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_69f34992ad40819087760ed939bd2a7a completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7004f4d9c8190b6517493f08084d4 completed May 3, 2026, 7:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a366eaf7a7081909ae0fd0f1e4e6e5e completed June 20, 2026, 10:42 a.m.
NEDg Description generation batch_6a366f45cc34819085bc33795237af77 completed June 20, 2026, 10:45 a.m.
NED2 Entity disambiguation (via description) batch_6a36710b582c8190a9510e1ab6c5d1e0 completed June 20, 2026, 10:52 a.m.
Created at: May 1, 2026, 1:47 a.m.