Triple
T16057797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trials World Championships |
E389526
|
entity |
| Predicate | skillRequired |
P6204
|
FINISHED |
| Object | balance |
—
|
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: balance | Statement: [Trials World Championships, skillRequired, balance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skillRequired Context triple: [Trials World Championships, skillRequired, balance]
-
A.
requiresSkill
chosen
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
B.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
C.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
D.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
E.
techniqueRequired
Indicates that performing one entity (such as an action, process, or task) necessitates the use of a specific technique associated with the other 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_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. |
Created at: April 10, 2026, 4:57 a.m.