Triple
T5442761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Division of the Superior Court of Guam |
E122174
|
entity |
| Predicate | caseCategory |
P87
|
FINISHED |
| Object | tort law |
—
|
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: tort law | Statement: [Civil Division of the Superior Court of Guam, caseCategory, tort law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseCategory Context triple: [Civil Division of the Superior Court of Guam, caseCategory, tort law]
-
A.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
B.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
C.
generalCategory
Indicates that one entity is classified as a broad or overarching category to which the other entity belongs.
-
D.
legalCaseAlongside
Indicates that two or more legal cases are proceeding in parallel or in coordination, such that they are related or handled together in some aspect of the legal process.
-
E.
officeCategory
Indicates the classification or type of an office within a defined categorization scheme.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.