Triple
T33723338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haile Gebrselassie |
E864076
|
entity |
| Predicate | ranForClub |
P84394
|
FINISHED |
| Object | Ethiopian national athletics team |
—
|
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: Ethiopian national athletics team | Statement: [Haile Gebrselassie, ranForClub, Ethiopian national athletics team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ranForClub Context triple: [Haile Gebrselassie, ranForClub, Ethiopian national athletics team]
-
A.
privateClub
Indicates that an entity is a club or organization whose membership or access is restricted to selected or approved individuals rather than being open to the general public.
-
B.
trainingClub
Indicates that one entity serves as a club or organization where the other entity receives training.
-
C.
mainClub2
chosen
Indicates that an entity serves as the primary or main club associated with another entity (such as a person, player, or organization).
-
D.
representsClub
Indicates that one entity serves as an official representative or delegate of a particular club.
-
E.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6faee25ec8190882de630051035a5 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.