Triple
T29986965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE membership grades |
E761757
|
entity |
| Predicate | entryLevelGrade |
P98368
|
FINISHED |
| Object | IEEE Student Member |
—
|
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: IEEE Student Member | Statement: [IEEE membership grades, entryLevelGrade, IEEE Student Member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryLevelGrade Context triple: [IEEE membership grades, entryLevelGrade, IEEE Student Member]
-
A.
eligibilityGradeLevel
Indicates the grade level or range of grade levels for which an entity is considered eligible or appropriate.
-
B.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
-
C.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
D.
eligibleGradeLevels
chosen
Indicates the grade levels for which something (such as a program, course, or benefit) is considered eligible or applicable.
-
E.
entryLevelCredential
Indicates that a credential qualifies someone for initial or beginner-level entry into a field, role, or program.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679173f38819089b99a9a98c9001f |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:37 p.m.