Triple
T16057801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trials World Championships |
E389526
|
entity |
| Predicate | noFootDownRule |
P121457
|
FINISHED |
| Object | central rule of the discipline |
—
|
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: central rule of the discipline | Statement: [Trials World Championships, noFootDownRule, central rule of the discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noFootDownRule Context triple: [Trials World Championships, noFootDownRule, central rule of the discipline]
-
A.
hasFootCrossing
Indicates that one entity has a designated crossing point specifically intended for pedestrians on foot.
-
B.
requiresShoesOff
Indicates that one entity mandates another to remove their shoes, typically as a condition for entry or participation.
-
C.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
D.
dropFeet
Indicates that an entity lowers or places its feet down, typically from a raised or suspended position.
-
E.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e185879c10819080a18e24969b5a6d |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:57 a.m.