Triple
T37843398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma Bar Association |
E943535
|
entity |
| Predicate | isBarFor |
P55337
|
FINISHED |
| Object | Oklahoma state courts |
—
|
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 state courts | Statement: [Oklahoma Bar Association, isBarFor, Oklahoma state courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBarFor Context triple: [Oklahoma Bar Association, isBarFor, Oklahoma state courts]
-
A.
hasBarService
chosen
Indicates that one entity provides or features bar service for another entity or at a given location.
-
B.
hasBarStrength
Indicates that one entity possesses or exhibits a certain level or measure of bar-related strength or robustness in relation to another entity or context.
-
C.
hasBars
Indicates that one entity possesses, contains, or is equipped with bars as a defining feature or component.
-
D.
isBarrierTo
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
E.
hasBarLength
Indicates that an entity possesses a bar whose length is specified or measured.
- 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_69f76eeb0f7081908d6d3adbc469889c |
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.