Triple
T3343830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Bar |
E70321
|
entity |
| Predicate | appliesRulesTo |
P8188
|
FINISHED |
| Object | lawyers admitted to practice in New York State |
—
|
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: lawyers admitted to practice in New York State | Statement: [New York State Bar, appliesRulesTo, lawyers admitted to practice in New York State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesRulesTo Context triple: [New York State Bar, appliesRulesTo, lawyers admitted to practice in New York State]
-
A.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
B.
appliesOver
Indicates that one entity’s effect, rule, or condition extends across or is valid for a specified range, domain, or set of entities.
-
C.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
setsRulesFor
chosen
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f23008819084ea68b8431c50ab |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.