Triple
T23090228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 101-476 |
E575724
|
entity |
| Predicate | addsDisabilityCategory |
P63365
|
FINISHED |
| Object | autism |
—
|
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: autism | Statement: [Public Law 101-476, addsDisabilityCategory, autism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsDisabilityCategory Context triple: [Public Law 101-476, addsDisabilityCategory, autism]
-
A.
disabilityCategories
chosen
Indicates that there is a relationship specifying which disability category or categories are associated with a given entity.
-
B.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
C.
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.
-
D.
disability
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
E.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da99bec81908ecadf8dab10d1b7 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.