Triple
T29602560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric |
E754488
|
entity |
| Predicate | targetAgeRangeOfWorkAppearsIn |
P177536
|
FINISHED |
| Object | Middle-grade readers |
—
|
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: Middle-grade readers | Statement: [Eric, targetAgeRangeOfWorkAppearsIn, Middle-grade readers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetAgeRangeOfWorkAppearsIn Context triple: [Eric, targetAgeRangeOfWorkAppearsIn, Middle-grade readers]
-
A.
focusesOnAgeRange
chosen
Indicates that something is specifically directed toward, concerned with, or tailored to a particular age range.
-
B.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
C.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
D.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
E.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 6:23 p.m.