Triple
T19852489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Accounting |
E477033
|
entity |
| Predicate | maySatisfyRequirementFor |
P110232
|
FINISHED |
| Object | CPA exam eligibility |
—
|
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: CPA exam eligibility | Statement: [Master of Accounting, maySatisfyRequirementFor, CPA exam eligibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySatisfyRequirementFor Context triple: [Master of Accounting, maySatisfyRequirementFor, CPA exam eligibility]
-
A.
mayProvideFor
Indicates that one entity is permitted or has the option to supply, support, or otherwise furnish something for another entity.
-
B.
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).
-
C.
designedToMeetRequirement
Indicates that something has been intentionally created or configured in order to satisfy a specified requirement.
-
D.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
E.
hasHigherListingRequirementsThan
Indicates that one entity is subject to stricter or more demanding listing requirements than another 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65869e1b481908e2a2a2074ff4a6d |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.