Triple
T33211182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Board on Judicial Conduct |
E850163
|
entity |
| Predicate | fictionalInWork |
P86934
|
FINISHED |
| Object | The Whistler |
—
|
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: The Whistler | Statement: [Florida Board on Judicial Conduct, fictionalInWork, The Whistler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalInWork Context triple: [Florida Board on Judicial Conduct, fictionalInWork, The Whistler]
-
A.
workInFiction
chosen
Indicates that one entity is a fictional work in which the other entity appears or is set.
-
B.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
C.
fictionalMaterial
Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
-
D.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
E.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 1, 2026, 1:30 a.m.