Triple
T4789925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Intercollegiate Athletic Association |
E106575
|
entity |
| Predicate | hasRuleFramework |
P14807
|
FINISHED |
| Object | NCAA 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: NCAA rules | Statement: [Central Intercollegiate Athletic Association, hasRuleFramework, NCAA rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuleFramework Context triple: [Central Intercollegiate Athletic Association, hasRuleFramework, NCAA rules]
-
A.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
isRuleGoverned
chosen
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
C.
canFrameRules
Indicates that one entity is able to define or establish the governing rules or framework that apply to another entity or context.
-
D.
hasRulebook
Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
-
E.
hasOrganizationFramework
Indicates that an entity is associated with, governed by, or operates under a particular organizational framework, structure, or governance model.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65dce6888190a0b1bdf416fb62b9 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.