Triple
T3766340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMX freestyle |
E82685
|
entity |
| Predicate | hasScoringCriterion |
P36515
|
FINISHED |
| Object | difficulty |
—
|
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: difficulty | Statement: [BMX freestyle, hasScoringCriterion, difficulty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoringCriterion Context triple: [BMX freestyle, hasScoringCriterion, difficulty]
-
A.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
B.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
C.
hasSubcriterion
Indicates that a criterion includes another, more specific criterion as a subordinate part of its evaluation structure.
-
D.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
E.
evaluationCriteriaInclude
chosen
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc0004608190a810ae0270ae2478 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.