Triple
T37848958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma Reports |
E943981
|
entity |
| Predicate | publishedForCourt |
P4014
|
FINISHED |
| Object | Oklahoma Supreme Court |
—
|
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: Oklahoma Supreme Court | Statement: [Oklahoma Reports, publishedForCourt, Oklahoma Supreme Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedForCourt Context triple: [Oklahoma Reports, publishedForCourt, Oklahoma Supreme Court]
-
A.
publishedFor
chosen
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
B.
publishedTo
Indicates that something has been made publicly available or distributed to an audience, platform, or destination.
-
C.
publishedDocument
Indicates that an entity has formally issued or made a document publicly available.
-
D.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
E.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:19 p.m.