Triple
T3398113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale Bulldogs women’s rowing |
E71578
|
entity |
| Predicate | alsoCompetesIn |
P39898
|
FINISHED |
| Object | fall head races |
—
|
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: fall head races | Statement: [Yale Bulldogs women’s rowing, alsoCompetesIn, fall head races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCompetesIn Context triple: [Yale Bulldogs women’s rowing, alsoCompetesIn, fall head races]
-
A.
competeIn
chosen
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
E.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c5816881909f91e6e9b81d29e3 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.