Triple
T13529992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BUCS Regatta |
E323106
|
entity |
| Predicate | rankingRole |
P110719
|
FINISHED |
| Object | contributes to BUCS rowing points table |
—
|
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: contributes to BUCS rowing points table | Statement: [BUCS Regatta, rankingRole, contributes to BUCS rowing points table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingRole Context triple: [BUCS Regatta, rankingRole, contributes to BUCS rowing points table]
-
A.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
C.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
D.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
E.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafba2c308190873efd15dfe26358 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.