Triple
T35526729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 |
E1026690
|
entity |
| Predicate | primaryRuleset |
P207028
|
FINISHED |
| Object | K-1 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: K-1 rules | Statement: [K-1, primaryRuleset, K-1 rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRuleset Context triple: [K-1, primaryRuleset, K-1 rules]
-
A.
priorityRule
Indicates that one entity is given precedence or higher processing order over another according to a defined rule or policy.
-
B.
primarySettingOf
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
-
C.
primaryStyle
Indicates the main or predominant style associated with an entity, distinguishing it from other secondary or supporting styles.
-
D.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.