Triple
T21927488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juris Doctor |
E541478
|
entity |
| Predicate | enablesEligibilityFor |
P110232
|
FINISHED |
| Object | bar examination |
—
|
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: bar examination | Statement: [Juris Doctor, enablesEligibilityFor, bar examination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesEligibilityFor Context triple: [Juris Doctor, enablesEligibilityFor, bar examination]
-
A.
mayProvideEligibilityFor
chosen
Indicates that one entity can serve as a basis or qualifying factor that makes another entity eligible for something (such as a benefit, status, or action).
-
B.
protectsEligibilityFor
Indicates that one entity preserves or safeguards another entity’s qualification or right to receive a particular benefit, status, or opportunity.
-
C.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
alsoEligible
Indicates that an entity qualifies for an additional option, status, or benefit beyond its primary or initial eligibility.
-
E.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123fc188481909c74fd5f1bd52258 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:46 p.m.