Triple
T13800458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISU Judging System |
E331624
|
entity |
| Predicate | judgingPanelRole |
P18875
|
FINISHED |
| Object | assign Grade of Execution |
—
|
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: assign Grade of Execution | Statement: [ISU Judging System, judgingPanelRole, assign Grade of Execution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgingPanelRole Context triple: [ISU Judging System, judgingPanelRole, assign Grade of Execution]
-
A.
roleInJudges
chosen
Indicates that an entity holds or held a specific role, position, or function within a judicial body or among a group of judges.
-
B.
partOfJudgingPanelWith
Indicates that two or more entities serve together as members of the same judging panel.
-
C.
juryRole
Indicates that an entity serves in the capacity or function of a juror within a judicial or decision-making process.
-
D.
hasJudgesRole
Indicates that an entity serves in the capacity or role of a judge within a specified context or system.
-
E.
presidingRole
Indicates that one entity holds an official position of authority or leadership over a proceeding, organization, or event involving 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.