Triple
T4185585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Journal of Physics |
E88302
|
entity |
| Predicate | audienceLevel |
P10804
|
FINISHED |
| Object | undergraduate |
—
|
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 | Statement: [American Journal of Physics, audienceLevel, undergraduate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceLevel Context triple: [American Journal of Physics, audienceLevel, undergraduate]
-
A.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
B.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
D.
developmentLevel
Indicates the degree or stage of progress, advancement, or maturity that something has reached in its growth or evolution.
-
E.
intendedReadingLevel
Indicates the reading proficiency or audience level that a text or resource is designed or meant to be understood by.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.