Triple
T162110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference USA |
E3309
|
entity |
| Predicate | usesRulesFrom |
P6249
|
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: [Conference USA, usesRulesFrom, NCAA rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRulesFrom Context triple: [Conference USA, usesRulesFrom, NCAA rules]
-
A.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
-
C.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
sharesRulesWith
Indicates that two entities follow, are governed by, or operate under the same set of rules or regulations.
-
E.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585877648190a2ec320182a69343 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2578329d08190be82e004b8224d2b |
completed | Feb. 28, 2026, 2:48 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.