Triple
T526407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Letter |
E10927
|
entity |
| Predicate | challengedIn |
P10247
|
FINISHED |
| Object | federal courts |
—
|
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: federal courts | Statement: [National Security Letter, challengedIn, federal courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: challengedIn Context triple: [National Security Letter, challengedIn, federal courts]
-
A.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
B.
challengedConcept
Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
-
C.
challengedStatute
chosen
Indicates that a particular statute or law is being contested, questioned, or disputed, typically in a legal or constitutional proceeding.
-
D.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
E.
defacedWith
Indicates that one entity has been damaged, marred, or vandalized using another entity as the means or material of defacement.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d0d22081908aad915482d39e74 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.