Triple
T31852985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | minor and family crimes section |
E813114
|
entity |
| Predicate | mayAlsoHandle |
P172668
|
FINISHED |
| Object | protective order violations |
—
|
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: protective order violations | Statement: [minor and family crimes section, mayAlsoHandle, protective order violations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoHandle Context triple: [minor and family crimes section, mayAlsoHandle, protective order violations]
-
A.
mayAlsoInclude
Indicates that something can optionally contain or encompass additional elements beyond those primarily specified.
-
B.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
-
C.
mayMatch
Indicates a potential or permissible correspondence or pairing between two entities, without guaranteeing that the match actually occurs.
-
D.
mayAlsoAdmit
Indicates that an entity has the option or authority to additionally allow or accept another entity, beyond any primary or default admission.
-
E.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03f3b148190a1b096da2a6c5864 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:51 p.m.