Triple
T27086923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman |
E686059
|
entity |
| Predicate | primaryScoringActions |
P198724
|
FINISHED |
| Object | throws |
—
|
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: throws | Statement: [Greco-Roman, primaryScoringActions, throws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScoringActions Context triple: [Greco-Roman, primaryScoringActions, throws]
-
A.
primaryScoringStyle
Indicates the main method or approach by which an entity achieves or generates scores or points.
-
B.
primaryScoringRange
Indicates the main numerical interval or category within which an entity’s score or rating is evaluated or classified.
-
C.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
D.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
| PDg | Predicate description generation | batch_69ff02141dbc8190b00bcea2aa734b3a |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 27, 2026, 8:38 a.m.