Triple
T15998661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Figure Skating Championships |
E388040
|
entity |
| Predicate | pairsIntroduced |
P121228
|
FINISHED |
| Object | 1908 |
—
|
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: 1908 | Statement: [World Figure Skating Championships, pairsIntroduced, 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairsIntroduced Context triple: [World Figure Skating Championships, pairsIntroduced, 1908]
-
A.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
B.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
C.
commonPair
Indicates that two entities commonly occur together or are frequently associated as a pair in some shared context.
-
D.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
-
E.
couplesTo
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
- F. None of above. chosen
Provenance (4 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:55 a.m.