Triple
T35208868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOMQuad |
E1016614
|
entity |
| Predicate | supportsNonAxisAlignedGeometry |
P206877
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [DOMQuad, supportsNonAxisAlignedGeometry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNonAxisAlignedGeometry Context triple: [DOMQuad, supportsNonAxisAlignedGeometry, true]
-
A.
hasGeometry
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
B.
supportsBoundingBoxes
Indicates that an entity is capable of handling, displaying, or otherwise working with bounding box representations for objects or regions.
-
C.
areNonUniformConvexPolyhedra
Indicates that the related entities are convex polyhedra whose faces or structural properties are not all identical, making them non-uniform in shape or configuration.
-
D.
isProductGeometry
Indicates that one entity represents the geometric definition or shape of a product associated with another entity.
-
E.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.