Triple
T12070551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weyl tensor |
E287410
|
entity |
| Predicate | dimensionRequirement |
P73084
|
FINISHED |
| Object | manifold dimension ≥ 3 |
—
|
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: manifold dimension ≥ 3 | Statement: [Weyl tensor, dimensionRequirement, manifold dimension ≥ 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionRequirement Context triple: [Weyl tensor, dimensionRequirement, manifold dimension ≥ 3]
-
A.
dimensionRestriction
chosen
Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity or relationship.
-
B.
dimensionEquals
Indicates that two entities have exactly the same dimensional properties or measurements.
-
C.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
D.
dimension
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
E.
dimensionVariant
Indicates a relationship where one entity is a variant or alternative version of another with respect to certain dimensions or configurable attributes.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.