Triple
T28549673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Nations Cup |
E722845
|
entity |
| Predicate | organizedUnderRules |
P81027
|
FINISHED |
| Object | ISU rules |
—
|
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: ISU rules | Statement: [1997 Nations Cup, organizedUnderRules, ISU rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedUnderRules Context triple: [1997 Nations Cup, organizedUnderRules, ISU rules]
-
A.
organizedUnderRulesOf
chosen
Indicates that an activity, process, or entity is structured, governed, or conducted according to a specified set of rules or regulations.
-
B.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
C.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
D.
organizedWith
Indicates that entities are arranged, structured, or coordinated together as part of the same organizing scheme or effort.
-
E.
formedUnderRuleOf
Indicates that one entity was created, established, or came into existence while another entity held governing authority or was in power.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 3:42 a.m.