Triple
T33539126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Olympic wrestling team |
E859021
|
entity |
| Predicate | teamSelectionFrequency |
P177082
|
FINISHED |
| Object | every Olympic cycle |
—
|
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: every Olympic cycle | Statement: [United States Olympic wrestling team, teamSelectionFrequency, every Olympic cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSelectionFrequency Context triple: [United States Olympic wrestling team, teamSelectionFrequency, every Olympic cycle]
-
A.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
B.
teamSelectionAuthority
Indicates that an entity has the authority or responsibility to choose or determine the members of a team.
-
C.
allStarSelectionCount
Indicates the number of times an entity has been selected as an All-Star.
-
D.
gamesFrequency
Indicates how often the related entities engage in playing games together or participate in game-related activities.
-
E.
matchupFrequency
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
- F. None of above. chosen
Provenance (4 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85ca7c0819098069384b0d1ca6a |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:39 a.m.