Triple
T1129975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High-A |
E23005
|
entity |
| Predicate | relativeDifficultyComparedTo |
P16772
|
FINISHED |
| Object | higher than Single-A |
—
|
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: higher than Single-A | Statement: [High-A, relativeDifficultyComparedTo, higher than Single-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeDifficultyComparedTo Context triple: [High-A, relativeDifficultyComparedTo, higher than Single-A]
-
A.
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.
-
B.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
C.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
D.
relativeComfort
Indicates a comparative relationship where one entity is judged to be more or less comfortable than another under given conditions.
-
E.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.