Triple
T9548904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Thorson |
E230367
|
entity |
| Predicate | legalActionFiled |
P89736
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Scott Thorson, legalActionFiled, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalActionFiled Context triple: [Scott Thorson, legalActionFiled, 1982]
-
A.
hasLegalProceeding
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
B.
filedWith
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
-
C.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
D.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
E.
legalActionReason
Indicates the reason, cause, or grounds for which a particular legal action is initiated or taken.
- F. None of above. chosen
Provenance (4 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_69ca847c70b8819088a0a0bad64a50d6 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99059138819088ae54b26df979cf |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:02 p.m.