Triple
T23933541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klebanov–Tseytlin background |
E602565
|
entity |
| Predicate | worldvolumeDimension |
P154407
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Klebanov–Tseytlin background, worldvolumeDimension, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldvolumeDimension Context triple: [Klebanov–Tseytlin background, worldvolumeDimension, 4]
-
A.
formationDimension
Indicates the dimensional characteristics (such as size, scale, or extent) associated with the formation of something.
-
B.
worldNumber
Indicates the specific world, dimension, or universe identifier associated with an entity or event.
-
C.
externalDimension
Indicates that an entity has a measurable size or extent along one or more outer spatial dimensions (such as length, width, or height).
-
D.
volumeOf
Indicates the quantitative three-dimensional space occupied by an entity or contained within an object.
-
E.
boundaryDimension
Indicates the dimensionality of the boundary of an entity, such as whether its boundary is a point, line, surface, or higher-dimensional analogue.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9da9c4819085880c6ad521d7ed |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:59 p.m.