Triple
T25683487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAT |
E644002
|
entity |
| Predicate | selectionProcessComponent |
P58007
|
FINISHED |
| Object | shortlisting for personal interviews |
—
|
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: shortlisting for personal interviews | Statement: [CAT, selectionProcessComponent, shortlisting for personal interviews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionProcessComponent Context triple: [CAT, selectionProcessComponent, shortlisting for personal interviews]
-
A.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
B.
selectionComponents
chosen
Indicates that certain elements function as constituent parts or options within a larger selection or choice.
-
C.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
E.
selectionProcessAbbreviation
Indicates that one entity is an abbreviation or shortened form used to refer to a particular selection process.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 8:04 p.m.