Triple
T27086940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman |
E686059
|
entity |
| Predicate | scoringTerm |
P162048
|
FINISHED |
| Object | grand amplitude throw |
—
|
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: grand amplitude throw | Statement: [Greco-Roman, scoringTerm, grand amplitude throw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoringTerm Context triple: [Greco-Roman, scoringTerm, grand amplitude throw]
-
A.
scoringTerm
chosen
Indicates that one entity is a term or expression used to assign, represent, or influence a score or rating in relation to another entity.
-
B.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
C.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
D.
scoringRecord
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
-
E.
scoringUnit
Indicates that one entity functions as a unit or component responsible for scoring or assigning scores 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:38 a.m.