Triple
T19751717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Mack |
E474392
|
entity |
| Predicate | legalDefenseBasedOn |
P125
|
FINISHED |
| Object | self-defense |
—
|
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: self-defense | Statement: [Joe Mack, legalDefenseBasedOn, self-defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDefenseBasedOn Context triple: [Joe Mack, legalDefenseBasedOn, self-defense]
-
A.
legalRepresentation
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
-
B.
defenseLawyer
Indicates that one entity serves as the legal representative defending another entity in a legal proceeding or case.
-
C.
legalProtectionFor
Indicates that one entity provides or is subject to legal safeguards, rights, or defenses in favor of another entity or interest.
-
D.
defendedLawProvision
Indicates that an entity actively supported or argued in favor of a specific provision within a law, typically in a legal or legislative context.
-
E.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65299a7048190a9b22307ac06bd03 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.