Triple
T26573285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyson Timbs |
E666882
|
entity |
| Predicate | propertySeizureType |
P162165
|
FINISHED |
| Object | civil asset forfeiture |
—
|
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: civil asset forfeiture | Statement: [Tyson Timbs, propertySeizureType, civil asset forfeiture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertySeizureType Context triple: [Tyson Timbs, propertySeizureType, civil asset forfeiture]
-
A.
canBeSeizedBy
Indicates that one entity is legally or physically able to be taken control of, captured, or confiscated by another entity.
-
B.
seizedCapital
Indicates that one entity forcibly took control of another entity’s capital city.
-
C.
evictionType
Indicates the specific kind or category of eviction that applies in a given eviction event or relationship.
-
D.
collateralType
Indicates the kind or category of collateral associated with an obligation, agreement, or financial exposure.
-
E.
confiscatedBy
Indicates that something has been taken away and seized by an authority or agent, typically as a legal or disciplinary action.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 1:59 a.m.