Triple
T13800469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISU Judging System |
E331624
|
entity |
| Predicate | technicalElementType |
P86564
|
FINISHED |
| Object | jumps |
—
|
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: jumps | Statement: [ISU Judging System, technicalElementType, jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technicalElementType Context triple: [ISU Judging System, technicalElementType, jumps]
-
A.
technicalType
Indicates the specific technical category or classification that characterizes how something is implemented, structured, or functions.
-
B.
toolType
Indicates the specific kind or category of tool associated with an entity.
-
C.
hasTechnicalElement
chosen
Indicates that something includes, involves, or is characterized by a technical component, feature, or aspect.
-
D.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
E.
circuitType
Indicates the specific kind or category of electrical circuit associated with an 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.