Triple
T35507471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIMC |
E1026188
|
entity |
| Predicate | admissionTestUsed |
P22453
|
FINISHED |
| Object | Common Admission Test |
—
|
NE NERFINISHED |
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: Common Admission Test | Statement: [IIMC, admissionTestUsed, Common Admission Test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionTestUsed Context triple: [IIMC, admissionTestUsed, Common Admission Test]
-
A.
enteredTesting
Indicates that an entity has begun or been moved into a testing phase, state, or environment.
-
B.
entranceExam
chosen
Indicates that an entity is required to pass or participate in an entrance examination as a condition for admission or access to another entity.
-
C.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
D.
admissionsStandard
Indicates that there is a specified criterion or set of requirements that must be met for admission to a program, institution, or opportunity.
-
E.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.