Triple
T3358705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patent Trial and Appeal Board |
E70664
|
entity |
| Predicate | procedureType |
P25382
|
FINISHED |
| Object | adversarial trial-like proceedings |
—
|
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: adversarial trial-like proceedings | Statement: [Patent Trial and Appeal Board, procedureType, adversarial trial-like proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: procedureType Context triple: [Patent Trial and Appeal Board, procedureType, adversarial trial-like proceedings]
-
A.
processType
Indicates the specific kind or category of process that an entity or activity belongs to.
-
B.
typeOfProceedings
chosen
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
C.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
-
D.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
E.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26523cc819091006fde7beb32e4 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.