Triple
T29694226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M5-branes |
E751297
|
entity |
| Predicate | bulkSpacetimeDimension |
P3642
|
FINISHED |
| Object | 11 |
—
|
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 | Statement: [M5-branes, bulkSpacetimeDimension, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bulkSpacetimeDimension Context triple: [M5-branes, bulkSpacetimeDimension, 11]
-
A.
spacetimeDimensionAssumed
chosen
Indicates that a specific number of spacetime dimensions is being taken as an assumption or working premise in a given context or model.
-
B.
worldvolumeDimension
Indicates the number of dimensions of the extended space (worldvolume) in which an object or brane exists or evolves.
-
C.
formationDimension
Indicates the dimensional characteristics (such as size, scale, or extent) associated with the formation of something.
-
D.
dimensionCount
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
E.
cosmicDimension
Indicates a relationship where something exists, operates, or is characterized within a particular cosmic or universal scale, realm, or dimension.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:19 p.m.