Triple
T2764068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steinmetz solid |
E61291
|
entity |
| Predicate | hasAxisConfiguration |
P43001
|
FINISHED |
| Object | cylinder axes intersect at right angles |
—
|
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: cylinder axes intersect at right angles | Statement: [Steinmetz solid, hasAxisConfiguration, cylinder axes intersect at right angles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAxisConfiguration Context triple: [Steinmetz solid, hasAxisConfiguration, cylinder axes intersect at right angles]
-
A.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
C.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
D.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
-
E.
hasTableConfiguration
Indicates that an entity is associated with or defined by a specific arrangement or setup of a table and its properties.
- 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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfc5e1c8190a5ac2c48d3eaeb0a |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddcc348081908b5f760899389d4f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:57 p.m.