Triple
T221250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Enforcement |
E4217
|
entity |
| Predicate | usesProcedure |
P7077
|
FINISHED |
| Object | informal inquiries |
—
|
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: informal inquiries | Statement: [Division of Enforcement, usesProcedure, informal inquiries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProcedure Context triple: [Division of Enforcement, usesProcedure, informal inquiries]
-
A.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
B.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
legalProcedureUsed
chosen
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
E.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25efd0df48190b8fef4c422a1265f |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b54d790819093b35bd1a6f00f92 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.