Triple
T14393282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CHI Conference |
E356895
|
entity |
| Predicate | acceptanceRate |
P738
|
FINISHED |
| Object | competitive |
—
|
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: competitive | Statement: [CHI Conference, acceptanceRate, competitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptanceRate Context triple: [CHI Conference, acceptanceRate, competitive]
-
A.
admitsStudentsFrom
Indicates that an educational institution accepts or enrolls students who come from a specified source, such as a school, region, or program.
-
B.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
C.
acceptsStudents
Indicates that an institution or program allows and takes in students as participants or members.
-
D.
typicalAdmissionSelectivity
chosen
Indicates the usual level of competitiveness or restrictiveness in admitting applicants to an institution or program.
-
E.
admittedStudents
Indicates that certain students have been officially accepted or granted admission to an institution, program, or course.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902b9acc8190817ffa848a76a880 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.