Triple
T37510732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | intake and records division |
E932208
|
entity |
| Predicate | recordTypeManaged |
P48884
|
FINISHED |
| Object | civil case records |
—
|
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: civil case records | Statement: [intake and records division, recordTypeManaged, civil case records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordTypeManaged Context triple: [intake and records division, recordTypeManaged, civil case records]
-
A.
recordsManagedBy
Indicates that certain records are overseen, maintained, or administered by a specified managing entity.
-
B.
recordTypeCode
Indicates the specific classification or category assigned to a record within a system or dataset.
-
C.
recordsType
chosen
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
D.
identifierTypeManaged
Indicates that one entity is responsible for administering or controlling the type or scheme of identifiers used for another entity.
-
E.
standardTypeManaged
Indicates that an entity is governed, controlled, or handled according to a defined standard type or classification.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.