Triple
T37848960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okla. Rep. |
E943981
|
entity |
| Predicate | citationScheme |
P49398
|
FINISHED |
| Object | American legal citation |
—
|
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: American legal citation | Statement: [Okla. Rep., citationScheme, American legal citation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citationScheme Context triple: [Okla. Rep., citationScheme, American legal citation]
-
A.
citationType
Indicates the specific kind or category of citation relationship that one entity has to another (e.g., reference, quotation, acknowledgment).
-
B.
citationSystem
chosen
Indicates a relationship where one entity specifies or uses a particular system, style, or standard for formatting and managing citations.
-
C.
citationAs
Indicates that one entity is cited or referenced in the role or capacity specified by another entity (such as a particular work, version, or context).
-
D.
citationRecord
Indicates that there exists a record documenting that one entity has cited or referenced another entity.
-
E.
citationBy
Indicates that one work is cited or referenced by another work.
- 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_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.