Triple
T12516621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cmp |
E299205
|
entity |
| Predicate | comparisonLevel |
P105406
|
FINISHED |
| Object | byte-level |
—
|
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: byte-level | Statement: [cmp, comparisonLevel, byte-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparisonLevel Context triple: [cmp, comparisonLevel, byte-level]
-
A.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
B.
comparisonProperty
Indicates that one entity is being compared to another based on a specific shared property or attribute.
-
C.
comparisonResult
Indicates the outcome of comparing two entities, typically expressing whether one is less than, equal to, or greater than the other.
-
D.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
E.
featureLevelComparedTo
Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954b715fc819091fa84430be46273 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 8, 2026, 9:57 p.m.