Triple
T7229949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck units |
E154875
|
entity |
| Predicate | characteristicScaleFor |
P46165
|
FINISHED |
| Object | quantum gravity effects |
—
|
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: quantum gravity effects | Statement: [Planck units, characteristicScaleFor, quantum gravity effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicScaleFor Context triple: [Planck units, characteristicScaleFor, quantum gravity effects]
-
A.
associatedScale
chosen
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
-
B.
dimensionCharacteristic
Indicates that one entity specifies or describes a dimensional property or measurement characteristic of another entity.
-
C.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
D.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
E.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea0d9b6c8190a0b5f0ab8d5cca19 |
completed | March 27, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.