Triple
T27676465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levin Papantonio Rafferty |
E697790
|
entity |
| Predicate | litigationScope |
P25835
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [Levin Papantonio Rafferty, litigationScope, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: litigationScope Context triple: [Levin Papantonio Rafferty, litigationScope, national]
-
A.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
B.
legalScope
chosen
Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
-
C.
litigates
Indicates that one party engages in legal action or conducts a lawsuit against or involving another party.
-
D.
legalProtectionScope
Indicates the extent and boundaries of rights, interests, or activities that are covered and safeguarded under a particular legal protection.
-
E.
legalDisputeSubject
Indicates that a legal dispute concerns, involves, or is specifically about the referenced subject or matter.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635339e888190bd1e33a0af531a38 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:44 p.m.