Triple
T28103693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autumn Scardina |
E710304
|
entity |
| Predicate | filedLawsuitIn |
P30230
|
FINISHED |
| Object | Colorado |
—
|
NE NERFINISHED |
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: Colorado | Statement: [Autumn Scardina, filedLawsuitIn, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filedLawsuitIn Context triple: [Autumn Scardina, filedLawsuitIn, Colorado]
-
A.
legalActionFiled
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or court.
-
B.
filedWith
chosen
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
-
C.
hasLegalProceeding
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
D.
litigatesBefore
Indicates that a legal case or dispute is argued or conducted in front of a particular court or judicial body.
-
E.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64093968c8190a76fb2261ed9f0a8 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:06 p.m.