Triple
T16717970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPIC |
E406271
|
entity |
| Predicate | applicants |
P93112
|
FINISHED |
| Object | individual children |
—
|
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: individual children | Statement: [OPIC, applicants, individual children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicants Context triple: [OPIC, applicants, individual children]
-
A.
applicantIn
Indicates that a person or entity is serving as an applicant within a particular context, process, or organization.
-
B.
applicant
chosen
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.
-
C.
eligibleAppointees
Indicates that certain individuals or entities meet the required criteria to be considered for a particular appointment or position.
-
D.
applicantType
Indicates the classification or category of an applicant in relation to an application or selection process.
-
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865799848190af919dccde958ee4 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.