Triple
T22099592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn heavyweight rowing |
E546132
|
entity |
| Predicate | hasRowingCategory |
P113140
|
FINISHED |
| Object | varsity eight |
—
|
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 eight | Statement: [Penn heavyweight rowing, hasRowingCategory, varsity eight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRowingCategory Context triple: [Penn heavyweight rowing, hasRowingCategory, varsity eight]
-
A.
hasRowingCourse
Indicates that one entity provides or includes a rowing course for another entity or at a given location.
-
B.
hasRowingSide
Indicates that an entity involved in rowing is associated with a specific side (e.g., port or starboard) on which it rows.
-
C.
isOlympicRowingCourse
Indicates that a location functions as an officially designated course used for Olympic rowing competitions.
-
D.
conferenceRowing
Indicates a relationship where a conference event or organization is engaged in, hosting, or associated with the sport or activity of rowing.
-
E.
typeOfRower
chosen
Indicates that one entity is a specific kind or category of rower in relation to 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291440048190992c48893ced0b34 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.