Triple
T3487312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantwell family |
E73639
|
entity |
| Predicate | reasonForArrest |
P15395
|
FINISHED |
| Object | soliciting without a license |
—
|
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: soliciting without a license | Statement: [Cantwell family, reasonForArrest, soliciting without a license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForArrest Context triple: [Cantwell family, reasonForArrest, soliciting without a license]
-
A.
arrestedFor
chosen
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
B.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
C.
arrestedAt
Indicates that an entity was apprehended or taken into custody at a specific location or during a specific event or time.
-
D.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
-
E.
arrests
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9193688190aa0cbf87a7b99446 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.