Triple
T6451714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1889 Cleveland Street scandal |
E139882
|
entity |
| Predicate | chargeType |
P71082
|
FINISHED |
| Object | gross indecency |
—
|
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: gross indecency | Statement: [1889 Cleveland Street scandal, chargeType, gross indecency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeType Context triple: [1889 Cleveland Street scandal, chargeType, gross indecency]
-
A.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
B.
chargingInstrumentTypes
Indicates the types of instruments or tools used to perform a charging action in a given context.
-
C.
chargeName
Indicates the specific name or label assigned to a charge or accusation associated with an entity.
-
D.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
E.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b62cbc81908b7f1a0dc1ed3e1d |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c068cb3b888190812ed56f2fdd45ed |
completed | March 22, 2026, 10:10 p.m. |
Created at: March 22, 2026, 4:47 p.m.