Triple
T6015253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juvenile Court of Guam |
E133933
|
entity |
| Predicate | caseParticipants |
P2434
|
FINISHED |
| Object | juvenile offenders |
—
|
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: juvenile offenders | Statement: [Juvenile Court of Guam, caseParticipants, juvenile offenders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseParticipants Context triple: [Juvenile Court of Guam, caseParticipants, juvenile offenders]
-
A.
opposingParticipants
Indicates that the related entities are participants positioned in opposition to each other within the same interaction, event, or context.
-
B.
partyToCase
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
C.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
D.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f80ec108190ae9711727debb061 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.