Triple
T21082116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State DNA Index System |
E519394
|
entity |
| Predicate | subjectTypeIncluded |
P22381
|
FINISHED |
| Object | convicted offenders |
—
|
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: convicted offenders | Statement: [State DNA Index System, subjectTypeIncluded, convicted offenders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectTypeIncluded Context triple: [State DNA Index System, subjectTypeIncluded, convicted offenders]
-
A.
subjectType
chosen
Indicates the classification or category that defines what kind of entity the subject is.
-
B.
subjectGroup
Indicates that an entity functions as a group or collection that the subject belongs to or is categorized under.
-
C.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
D.
writtenExamSubjectsInclude
Indicates that the set of subjects specified is included among the subjects covered by a particular written exam.
-
E.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702db430c81908a1547d8fbe45506 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.