Triple
T99852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBA |
E2016
|
entity |
| Predicate | typicalApplicantBackground |
P4802
|
FINISHED |
| Object | business |
—
|
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: business | Statement: [MBA, typicalApplicantBackground, business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApplicantBackground Context triple: [MBA, typicalApplicantBackground, business]
-
A.
educatedAt
Indicates that an entity received education or formal training at a specified institution or place of learning.
-
B.
educationType
Indicates the specific category or level of education associated with an entity, such as formal, informal, primary, secondary, or higher education.
-
C.
typicalAdmissionSelectivity
Indicates the usual level of competitiveness or restrictiveness in admitting applicants to an institution or program.
-
D.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
-
E.
academicAdvisor
Indicates that one entity serves as the academic advisor, providing formal guidance and oversight on academic matters, to another entity.
- F. None of above. chosen
Provenance (4 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a253b869448190bd75a3542806b36c |
completed | Feb. 28, 2026, 2:32 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.