Triple
T602711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon State Beavers gymnastics team |
E11527
|
entity |
| Predicate | recruitingLevel |
P5414
|
FINISHED |
| Object | elite club and Level 10 gymnasts |
—
|
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: elite club and Level 10 gymnasts | Statement: [Oregon State Beavers gymnastics team, recruitingLevel, elite club and Level 10 gymnasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitingLevel Context triple: [Oregon State Beavers gymnastics team, recruitingLevel, elite club and Level 10 gymnasts]
-
A.
recruitingScope
Indicates the extent or boundaries within which recruiting activities are conducted or targeted.
-
B.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
C.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
D.
recruitmentBasis
chosen
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
E.
recruitingProfile
Indicates that an entity serves as or is associated with a recruiting profile used for hiring or talent acquisition activities.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49cf701e08190966d06b9ff4b582b |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.