Triple
T28309207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .300 AAC Blackout |
E713950
|
entity |
| Predicate | parentCase |
P3137
|
FINISHED |
| Object | .223 Remington |
—
|
NE NERFINISHED |
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: .223 Remington | Statement: [.300 AAC Blackout, parentCase, .223 Remington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCase Context triple: [.300 AAC Blackout, parentCase, .223 Remington]
-
A.
parentCourt
Indicates that one court is hierarchically above and has authority over another court within a judicial system.
-
B.
primaryCase
Indicates that an entity is the main or leading instance in a set of related cases or occurrences.
-
C.
relatedCase
chosen
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
D.
parentBureau
Indicates that one bureau has organizational authority over or is the supervising/owning bureau of another bureau.
-
E.
parentAct
Indicates that one entity performs an action in the role of a parent toward another entity, typically involving caregiving, guidance, or parental responsibility.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 11:39 p.m.