Triple
T7476533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noerr-Pennington doctrine |
E176644
|
entity |
| Predicate | usedAsDefenseIn |
P1135
|
FINISHED |
| Object | antitrust litigation |
—
|
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: antitrust litigation | Statement: [Noerr-Pennington doctrine, usedAsDefenseIn, antitrust litigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDefenseIn Context triple: [Noerr-Pennington doctrine, usedAsDefenseIn, antitrust litigation]
-
A.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
B.
typeOfDefense
chosen
Indicates the specific kind or category of defense employed or possessed in a given context.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
E.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4ee23d081908e05658a651661fc |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.