Triple
T8684849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-theory |
E206131
|
entity |
| Predicate | lowEnergyLimit |
P84173
|
FINISHED |
| Object | 11-dimensional supergravity |
—
|
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: 11-dimensional supergravity | Statement: [M-theory, lowEnergyLimit, 11-dimensional supergravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowEnergyLimit Context triple: [M-theory, lowEnergyLimit, 11-dimensional supergravity]
-
A.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
B.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
C.
hasLow
Indicates that an entity possesses a value, level, or amount of something that is below a defined or expected threshold.
-
D.
lowerValueIndicates
Indicates that a smaller numerical value of a property or measurement corresponds to a greater degree, better outcome, or stronger presence of the relevant characteristic.
-
E.
lowerFieldCharge
Indicates that an entity reduces or decreases the electric charge present in a specified field.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:32 p.m.