Triple
T31867275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suicide |
E813491
|
entity |
| Predicate | proposesTypologyOf |
P180357
|
FINISHED |
| Object | suicide |
—
|
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: suicide | Statement: [Suicide, proposesTypologyOf, suicide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesTypologyOf Context triple: [Suicide, proposesTypologyOf, suicide]
-
A.
typology
Indicates a classification relationship in which entities are grouped or organized according to shared types, patterns, or structural characteristics.
-
B.
theoryType
Indicates the classification relationship that specifies what type or category of theory an entity belongs to.
-
C.
arealTypology
Indicates a typological relationship based on geographic or areal distribution, showing how linguistic features are shared or patterned across regions.
-
D.
typologicalGroup
Indicates that entities are classified together based on shared structural or typological characteristics.
-
E.
conceptualType
Indicates that one entity represents the conceptual category, class, or abstract type to which another entity belongs.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 30, 2026, 11:54 p.m.