Triple
T26810845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ionic order |
E671987
|
entity |
| Predicate | shaftFeature |
P161494
|
FINISHED |
| Object | separated by fillets |
—
|
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: separated by fillets | Statement: [Ionic order, shaftFeature, separated by fillets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shaftFeature Context triple: [Ionic order, shaftFeature, separated by fillets]
-
A.
shaftFeature
chosen
Indicates a relationship where one object possesses or is characterized by a shaft-like structural feature.
-
B.
shaftHeight
Indicates the vertical extent or length of a shaft from its base to its top.
-
C.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
D.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
-
E.
shaftArrangement
Indicates how one or more shafts are positioned, oriented, or configured relative to each other within a mechanical or structural system.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 4:29 a.m.