Triple
T20222146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Cavaliers women's cross country |
E495281
|
entity |
| Predicate | squadLevel |
P5182
|
FINISHED |
| Object | varsity intercollegiate team |
—
|
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: varsity intercollegiate team | Statement: [Virginia Cavaliers women's cross country, squadLevel, varsity intercollegiate team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: squadLevel Context triple: [Virginia Cavaliers women's cross country, squadLevel, varsity intercollegiate team]
-
A.
teamLevel
chosen
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
B.
squadCharacteristic
Indicates that a particular characteristic, trait, or property is attributed to a squad as a whole.
-
C.
squadron
Indicates that an entity is organized into or associated with a specific squadron as a formal operational unit.
-
D.
squadSelectionBasis
Indicates the criterion or rationale used to choose which individuals are included in a particular squad or team.
-
E.
controlsTeamLevel
Indicates that one entity has authority or decision-making power over the overall direction, strategy, or functioning of a team.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd729548190942bcf842f03c4cd |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.