Triple
T15125131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ND Cal. |
E361265
|
entity |
| Predicate | caseLoadCharacteristic |
P50505
|
FINISHED |
| Object | high volume of technology and IP cases |
—
|
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: high volume of technology and IP cases | Statement: [ND Cal., caseLoadCharacteristic, high volume of technology and IP cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseLoadCharacteristic Context triple: [ND Cal., caseLoadCharacteristic, high volume of technology and IP cases]
-
A.
courtCharacteristic
chosen
Indicates that a specified attribute or quality is associated with, or descriptive of, a particular court.
-
B.
recordCharacteristic
Indicates that an entity documents or stores a specific characteristic or attribute of another entity.
-
C.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
D.
rulesCharacteristic
Indicates that one entity establishes or defines a characteristic, property, or feature that another entity must follow or conform to.
-
E.
issueCharacterization
Indicates how an issue, problem, or case is categorized or described in terms of its nature, type, or defining attributes.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a0c6888190840de4ead2306544 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.