Triple
T31592504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Municipal Courts |
E806136
|
entity |
| Predicate | casePartiesInclude |
P70474
|
FINISHED |
| Object | city prosecutors |
—
|
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: city prosecutors | Statement: [Arizona Municipal Courts, casePartiesInclude, city prosecutors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casePartiesInclude Context triple: [Arizona Municipal Courts, casePartiesInclude, city prosecutors]
-
A.
partyToCase
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
legalParties
chosen
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
-
C.
partiesAre
Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
-
D.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
E.
otherSignificantParty
Indicates that an entity has another important associated party, such as a key counterpart, partner, or involved participant in a relationship or transaction.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a83233a481908538a05365fbfd43 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:28 p.m.