Triple
T9564410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck length |
E230753
|
entity |
| Predicate | isQuantumGravityScale |
P34669
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Planck length, isQuantumGravityScale, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isQuantumGravityScale Context triple: [Planck length, isQuantumGravityScale, true]
-
A.
isQuantumOf
Indicates that one entity represents a discrete, indivisible unit or packet of the other entity in a quantized relationship.
-
B.
roleInQuantumGravity
chosen
Indicates that an entity has a specific function, status, or contribution within the theoretical framework or research program of quantum gravity.
-
C.
usesSymbolForGravitationalConstant
Indicates that an entity adopts a particular symbol to represent the gravitational constant in formulas or notation.
-
D.
cosmologicalScale
Indicates that the relationship or phenomenon is occurring, measured, or considered at the scale of the entire universe or its large-scale structure.
-
E.
isQuantumEffect
Indicates that the relationship or phenomenon arises specifically from quantum mechanical principles or effects rather than classical behavior.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9968b8608190b3078fe5764f0a69 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.