Triple
T896764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulysses |
E19362
|
entity |
| Predicate | legalHistory |
P20840
|
FINISHED |
| Object | subject of obscenity trials |
—
|
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: subject of obscenity trials | Statement: [Ulysses, legalHistory, subject of obscenity trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalHistory Context triple: [Ulysses, legalHistory, subject of obscenity trials]
-
A.
historicalLaw
Indicates that the referenced law or legal provision existed and was in effect during a past historical period, rather than being current.
-
B.
subsequentHistory
Indicates that one event, state, or record occurs or is recorded after another in time, reflecting its later historical development or outcome.
-
C.
historicalJurisdiction
Indicates that one entity previously held legal or administrative authority over another entity during a past time period.
-
D.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
-
E.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.