Triple
T1682349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSM-IV |
E36365
|
entity |
| Predicate | usesMultiaxialSystem |
P32704
|
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: [DSM-IV, usesMultiaxialSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMultiaxialSystem Context triple: [DSM-IV, usesMultiaxialSystem, true]
-
A.
isMajorAxisFor
Indicates that something serves as the primary or longest axis that defines the main directional or structural orientation of another object or system.
-
B.
isMultidisciplinary
Indicates that something involves or integrates multiple distinct academic or professional disciplines in its approach or composition.
-
C.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
D.
isIsotropic
Indicates that a property or behavior is identical in all directions, showing no directional dependence.
-
E.
isMultiPurpose
Indicates that something is designed or used to serve multiple functions or purposes rather than a single, specialized one.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba641e6a881909645577e72b53df2 |
completed | March 7, 2026, 4:14 a.m. |
Created at: March 4, 2026, 7:29 p.m.