Triple
T360769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fundamentals of Engineering exam |
E7845
|
entity |
| Predicate | typicalCandidate |
P12352
|
FINISHED |
| Object | undergraduate engineering student |
—
|
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: undergraduate engineering student | Statement: [Fundamentals of Engineering exam, typicalCandidate, undergraduate engineering student]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCandidate Context triple: [Fundamentals of Engineering exam, typicalCandidate, undergraduate engineering student]
-
A.
featuredCandidate
Indicates that a particular candidate is highlighted or given special prominence relative to others.
-
B.
electedCandidate
Indicates that a particular person has been chosen as the winner in an election for a given position or office.
-
C.
candidateNomination
Indicates that an individual is formally put forward or proposed as a candidate for a position, role, or office.
-
D.
opponentCandidate
Indicates that one entity is a rival or competing candidate against another in the same contest or election.
-
E.
mainCandidates
Indicates that the referenced entities are the primary or most prominent candidates within a given selection or context.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.