Triple
T4076273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Enforcement Executive Development programs |
E86770
|
entity |
| Predicate | typicallyInclude |
P44882
|
FINISHED |
| Object | classroom instruction |
—
|
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: classroom instruction | Statement: [Law Enforcement Executive Development programs, typicallyInclude, classroom instruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyInclude Context triple: [Law Enforcement Executive Development programs, typicallyInclude, classroom instruction]
-
A.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
traditionallyIncludes
chosen
Indicates that something customarily or historically contains or incorporates something else as a standard or expected part.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
E.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4ba3f08190a6c6aaf6e9c99bd5 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.