Triple
T37358236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O zittre nicht, mein lieber Sohn |
E927510
|
entity |
| Predicate | notableDifficulty |
P2406
|
FINISHED |
| Object | requires extreme agility |
—
|
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: requires extreme agility | Statement: [O zittre nicht, mein lieber Sohn, notableDifficulty, requires extreme agility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDifficulty Context triple: [O zittre nicht, mein lieber Sohn, notableDifficulty, requires extreme agility]
-
A.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
B.
typicalDifficulty
Indicates the usual or characteristic level of difficulty associated with performing an action or achieving a particular outcome.
-
C.
notableObstacle
Indicates that something serves as a significant hindrance, barrier, or challenge to achieving a goal or progressing in a situation.
-
D.
difficulty
chosen
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
E.
notableLevelType
Indicates that one entity is recognized as a notable or distinguished type or category of 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.