Triple
T23609288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongo |
E582989
|
entity |
| Predicate | hasDisabilityCause |
P11973
|
FINISHED |
| Object | result of incestuous abuse |
—
|
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: result of incestuous abuse | Statement: [Mongo, hasDisabilityCause, result of incestuous abuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisabilityCause Context triple: [Mongo, hasDisabilityCause, result of incestuous abuse]
-
A.
causeOfDisability
chosen
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
B.
disabilityAcquired
Indicates that a disability has been obtained or developed by an entity after an initial point in time, rather than being present from birth.
-
C.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
-
D.
disability
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
E.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f281d08190a1a713e9c24a2b23 |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:44 p.m.