Triple
T2091483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck length |
E32679
|
entity |
| Predicate | isSmallestMeaningfulScaleIn |
P34666
|
FINISHED |
| Object | many quantum gravity theories |
—
|
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: many quantum gravity theories | Statement: [Planck length, isSmallestMeaningfulScaleIn, many quantum gravity theories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSmallestMeaningfulScaleIn Context triple: [Planck length, isSmallestMeaningfulScaleIn, many quantum gravity theories]
-
A.
isMinimumWhen
Indicates that a value or state is at its smallest or least level precisely under certain specified conditions or circumstances.
-
B.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
C.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
D.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
E.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba7626d081908c9c0f18942e128d |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:43 p.m.