Triple
T3788396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Air Shougang |
E85583
|
entity |
| Predicate | usedAfterEvent |
P5014
|
FINISHED |
| Object | international winter sports competitions |
—
|
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: international winter sports competitions | Statement: [Big Air Shougang, usedAfterEvent, international winter sports competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAfterEvent Context triple: [Big Air Shougang, usedAfterEvent, international winter sports competitions]
-
A.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
B.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
subsequentUse
chosen
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d4bc3c81909bd56e33d43fa8e4 |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.