Triple
T13800591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISU Special Regulations and Technical Rules Single & Pair Skating and Ice Dance |
E331627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical rules document |
C34190
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: technical rules document Context triple: [ISU Special Regulations and Technical Rules Single & Pair Skating and Ice Dance, instanceOf, technical rules document]
-
A.
Technical specification
A technical specification is a detailed, formal document that precisely defines the functional, performance, and interface requirements of a system, component, or product to guide its design, implementation, and verification.
-
B.
technical report
A technical report is a structured document that presents methods, data, analysis, and conclusions about a specific technical or scientific investigation for a targeted audience.
-
C.
technical specification area
A technical specification area is a defined section within a system or document that outlines detailed technical requirements, standards, and constraints for a particular component, function, or domain.
-
D.
technical article
A technical article is a structured, in-depth written work that explains, analyzes, or documents specific technologies, methods, or scientific concepts for a knowledgeable audience.
-
E.
technical book
A technical book is a structured, in-depth written work that explains specialized concepts, methods, or technologies in a specific field, often combining theory with practical examples and applications.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: April 9, 2026, 10:11 p.m.