Triple
T12973080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super-G alpine skiing for men |
E321451
|
entity |
| Predicate | runFormat |
P130
|
FINISHED |
| Object | single timed run |
—
|
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: single timed run | Statement: [Super-G alpine skiing for men, runFormat, single timed run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runFormat Context triple: [Super-G alpine skiing for men, runFormat, single timed run]
-
A.
runwayFormat
Indicates the specific physical configuration or layout type of a runway used for takeoff and landing.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
D.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
E.
overseesFormat
Indicates that one entity is responsible for supervising, managing, or controlling the format or formatting standards of 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:36 p.m.