Triple
T25828865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck power |
E650604
|
entity |
| Predicate | isExtremelyLargeComparedTo |
P23282
|
FINISHED |
| Object | terrestrial power scales |
—
|
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: terrestrial power scales | Statement: [Planck power, isExtremelyLargeComparedTo, terrestrial power scales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExtremelyLargeComparedTo Context triple: [Planck power, isExtremelyLargeComparedTo, terrestrial power scales]
-
A.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
B.
isVeryCoarseComparedTo
Indicates that one entity has a much rougher or less fine texture, structure, or granularity than another entity.
-
C.
largerThan
Indicates that one entity has a greater size, extent, or magnitude than another entity.
-
D.
isHeavierThan
Indicates that one entity has greater weight or mass than another entity.
-
E.
scaleComparison
chosen
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6019807f08190bbeb8be744551fdf |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:37 a.m.