Triple
T12679377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Admission Test |
E302904
|
entity |
| Predicate | furtherAdmissionRounds |
P106242
|
FINISHED |
| Object | group discussion |
—
|
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: group discussion | Statement: [Common Admission Test, furtherAdmissionRounds, group discussion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherAdmissionRounds Context triple: [Common Admission Test, furtherAdmissionRounds, group discussion]
-
A.
admissionResult
Indicates the outcome or decision of an admission process for an applicant or entity.
-
B.
admissionOrder
Indicates the sequence or priority in which admissions occur or are processed relative to one another.
-
C.
admissionsBasedOn
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
-
D.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
E.
controlsAdmissionsFor
Indicates that one entity has authority or responsibility over managing and deciding admissions for 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_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. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:21 p.m.