Triple
T1696336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blacker |
E36665
|
entity |
| Predicate | comparisonType |
P31276
|
FINISHED |
| Object | relative comparison |
—
|
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: relative comparison | Statement: [Blacker, comparisonType, relative comparison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparisonType Context triple: [Blacker, comparisonType, relative comparison]
-
A.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
B.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
C.
historicalComparison
Indicates a relationship where one entity is evaluated or contrasted with another in terms of their characteristics, significance, or context across different historical periods.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
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. chosen
Provenance (4 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aaf16865488190a76577b36760dc7a |
completed | March 6, 2026, 3:23 p.m. |
Created at: March 4, 2026, 7:30 p.m.