Triple
T21477823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Azam |
E529908
|
entity |
| Predicate | degreeOfComparison |
P105406
|
FINISHED |
| Object | superlative |
—
|
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: superlative | Statement: [al-Azam, degreeOfComparison, superlative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degreeOfComparison Context triple: [al-Azam, degreeOfComparison, superlative]
-
A.
comparisonLevel
chosen
Indicates the degree or intensity to which two or more entities are being compared within a given context.
-
B.
comparativeScale
Indicates a relationship where one entity is evaluated relative to another along a shared scale or dimension (such as size, intensity, or degree).
-
C.
primaryComparison
Indicates that one entity is being used as the main reference point or standard against which another entity is compared.
-
D.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
E.
comparisonClass
Indicates that something is being evaluated or interpreted relative to a specified reference group or standard for comparison.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1951fc8190910f634327aa5c3f |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:20 p.m.