Triple
T10661690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi-Civita symbol |
E251240
|
entity |
| Predicate | in4Dimensions |
P6122
|
FINISHED |
| Object | ε_{ijkl} |
—
|
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: ε_{ijkl} | Statement: [Levi-Civita symbol, in4Dimensions, ε_{ijkl}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: in4Dimensions
Context triple: [Levi-Civita symbol, in4Dimensions, ε_{ijkl}]
-
A.
formationDimension
Indicates the dimensional characteristics (such as size, scale, or extent) associated with the formation of something.
-
B.
dimension
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
C.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
inGalacticQuadrant
Indicates that one entity (typically a location or object) is situated within a specified galactic quadrant in space.
-
E.
dimensionCount
chosen
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e018d1e881909b8e62682104e842 |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.