Triple
T13362873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelion |
E318861
|
entity |
| Predicate | difficultyComparedToBatian |
P16772
|
FINISHED |
| Object | similar technical 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: similar technical difficulty | Statement: [Nelion, difficultyComparedToBatian, similar technical difficulty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: difficultyComparedToBatian Context triple: [Nelion, difficultyComparedToBatian, similar technical difficulty]
-
A.
isEasierThan
Indicates that one entity requires less effort, difficulty, or complexity to accomplish, understand, or deal with than another entity.
-
B.
difficultyRelativeTo
chosen
Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
-
C.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
D.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
E.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628affd081909f1790d333f0eef4 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.