Triple
T27086987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Championships (Greco-Roman wrestling) |
E686060
|
entity |
| Predicate | hasIndividualScoring |
P81769
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [World Championships (Greco-Roman wrestling), hasIndividualScoring, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndividualScoring Context triple: [World Championships (Greco-Roman wrestling), hasIndividualScoring, yes]
-
A.
individualScoring
chosen
Indicates that a specific individual receives or is assigned a particular score or evaluation in a given context.
-
B.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
C.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
hasScoringUnit
Indicates that one entity possesses or is associated with a unit used for scoring, measurement, or point allocation in a given context.
-
E.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 27, 2026, 8:38 a.m.