Triple

T37471053
Position Surface form Disambiguated ID Type / Status
Subject Skoldus Hall E931152 entity
Predicate difficultyType P98685 FINISHED
Object scaling difficulty 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: scaling difficulty | Statement: [Skoldus Hall, difficultyType, scaling difficulty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: difficultyType
Context triple: [Skoldus Hall, difficultyType, scaling difficulty]
  • A. difficulty
    Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
  • B. difficultySource
    Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
  • C. difficultyOption chosen
    Indicates a relationship where a particular option specifies or represents a level of difficulty for something (e.g., a task, question, or activity).
  • D. difficultyRelativeTo
    Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
  • E. difficultyClassRange
    Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
  • 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_69f76ec2af148190897d101070d7f415 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb084760c8190a1554985d3c3cb7a completed May 6, 2026, 9:20 p.m.
PD Predicate disambiguation batch_69fbadf3cb548190ba3b7514f76b790a completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:17 p.m.