Triple
T1682513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | anxiety disorders |
E36368
|
entity |
| Predicate | includesSubtype |
P21666
|
FINISHED |
| Object | generalized anxiety disorder |
—
|
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: generalized anxiety disorder | Statement: [anxiety disorders, includesSubtype, generalized anxiety disorder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSubtype Context triple: [anxiety disorders, includesSubtype, generalized anxiety disorder]
-
A.
includesSuborder
Indicates that one entity contains or encompasses another entity as a subordinate order within its hierarchical structure.
-
B.
hasSubConcept
chosen
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
C.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
D.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
E.
isSubnetworkOf
Indicates that one network is a contained, subordinate, or component part of another, larger network.
- 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_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. |
Created at: March 4, 2026, 7:29 p.m.