Triple
T15561723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA women’s water polo |
E371015
|
entity |
| Predicate | usesGoverningRulesFrom |
P6249
|
FINISHED |
| Object | NCAA water polo 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 water polo rules | Statement: [NCAA women’s water polo, usesGoverningRulesFrom, NCAA water polo rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGoverningRulesFrom Context triple: [NCAA women’s water polo, usesGoverningRulesFrom, NCAA water polo rules]
-
A.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
B.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
C.
governingJurisdictionForRules
Indicates the legal or regulatory jurisdiction under whose authority a given set of rules or regulations applies.
-
D.
governingBodyForRules
Indicates that an entity serves as the official authority responsible for creating, maintaining, or enforcing a specified set of rules.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddb4c0c81909b3f4c75c91f7f3f |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.