Triple
T26775685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multistate Bar Examination |
E670112
|
entity |
| Predicate | isTakenBy |
P161229
|
FINISHED |
| Object | foreign-trained lawyers in some jurisdictions |
—
|
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: foreign-trained lawyers in some jurisdictions | Statement: [Multistate Bar Examination, isTakenBy, foreign-trained lawyers in some jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTakenBy Context triple: [Multistate Bar Examination, isTakenBy, foreign-trained lawyers in some jurisdictions]
-
A.
isTakenBy
chosen
Indicates that something (such as an object, resource, or opportunity) is received, acquired, or accepted by a particular entity.
-
B.
isTaken
Indicates that an entity has been captured, occupied, or claimed by another entity or force.
-
C.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
D.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
-
E.
takenBy
Indicates that something is captured, acquired, or received by a particular entity.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6193294948190adeecbad17283103 |
completed | May 2, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:04 a.m.