Triple
T27994623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Indoor Football League |
E706975
|
entity |
| Predicate | rulesDifferFrom |
P39866
|
FINISHED |
| Object | National Football League 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: National Football League rules | Statement: [Southern Indoor Football League, rulesDifferFrom, National Football League rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesDifferFrom Context triple: [Southern Indoor Football League, rulesDifferFrom, National Football League rules]
-
A.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
B.
hasRuleDifferenceFromNFL
chosen
Indicates that the subject’s rules differ in some way from those used in the NFL.
-
C.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
D.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
mayDifferFrom
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63ba9cfb48190acd2e4dbb31951f0 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:52 p.m.