Triple
T25435248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahara Conference |
E637355
|
entity |
| Predicate | hasTeamsType |
P2705
|
FINISHED |
| Object | club teams |
—
|
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: club teams | Statement: [Sahara Conference, hasTeamsType, club teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamsType Context triple: [Sahara Conference, hasTeamsType, club teams]
-
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.
typeOfTeams
chosen
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
C.
hasNotableTeamType
Indicates that an entity is associated with a team that is recognized as having a specific notable type or category.
-
D.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
E.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 1:59 p.m.