Triple
T12679363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Admission Test |
E302904
|
entity |
| Predicate | applicantPool |
P4145
|
FINISHED |
| Object | management aspirants across India |
—
|
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: management aspirants across India | Statement: [Common Admission Test, applicantPool, management aspirants across India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicantPool Context triple: [Common Admission Test, applicantPool, management aspirants across India]
-
A.
applicantIn
Indicates that a person or entity is serving as an applicant within a particular context, process, or organization.
-
B.
eligibleAppointees
Indicates that certain individuals or entities meet the required criteria to be considered for a particular appointment or position.
-
C.
applicant
Indicates that an entity plays the role of a person or organization formally applying for something (such as a job, program, or permit) from another entity.
-
D.
applicantType
Indicates the classification or category of an applicant in relation to an application or selection process.
-
E.
recruitmentFrom
chosen
Indicates that one entity recruits or sources members, employees, or participants from 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b1dff48190923290555ece5d89 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.