Triple
T173576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feynman checkerboard model |
E3528
|
entity |
| Predicate | spatialDimension |
P3642
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Feynman checkerboard model, spatialDimension, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spatialDimension Context triple: [Feynman checkerboard model, spatialDimension, 1]
-
A.
dimension
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
B.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
C.
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.
-
D.
allowsSpatialCurvature
Indicates that one entity permits or enables the presence or variation of spatial curvature in relation to another entity or context.
-
E.
hasSpacetimeRegion
Indicates that something occupies, is associated with, or is bounded by a specific region in spacetime.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e1ec008190a89dd452f72574f4 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.