Triple
T18977920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varsity Eight |
E464344
|
entity |
| Predicate | isScoredIn |
P103028
|
FINISHED |
| Object | team points standings at regattas |
—
|
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: team points standings at regattas | Statement: [Varsity Eight, isScoredIn, team points standings at regattas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScoredIn Context triple: [Varsity Eight, isScoredIn, team points standings at regattas]
-
A.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
B.
isPartOfScoreBy
Indicates that something constitutes a component or segment within a larger score or musical composition.
-
C.
scoredAsPartOf
chosen
Indicates that an entity achieved a score or rating specifically within the context of being part of a larger group, event, or composite activity.
-
D.
coScoredWith
Indicates that two or more entities received the same score or were evaluated with an identical scoring outcome in a shared context.
-
E.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d620bba48190a300dba9733592b0 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon