Triple
T22998467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landmark Conference |
E572569
|
entity |
| Predicate | competitionRuleSet |
P2673
|
FINISHED |
| Object | NCAA Division III 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 Division III rules | Statement: [Landmark Conference, competitionRuleSet, NCAA Division III rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionRuleSet Context triple: [Landmark Conference, competitionRuleSet, NCAA Division III rules]
-
A.
competitionSquadRule
Indicates the rules or constraints governing how squads or teams must be composed or registered for a particular competition.
-
B.
sportRules
Indicates that there is a set of rules or regulations governing how a particular sport is played or conducted.
-
C.
amateurismRulesSetBy
Indicates that one party establishes or defines the rules governing amateurism that another party is subject to or follows.
-
D.
competitionSystem
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
-
E.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f54ce88190930530958e2a1830 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.