Triple
T2397822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV Children’s Bible |
E47690
|
entity |
| Predicate | audienceAgeRange |
P10804
|
FINISHED |
| Object | elementary-age children |
—
|
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: elementary-age children | Statement: [ESV Children’s Bible, audienceAgeRange, elementary-age children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceAgeRange Context triple: [ESV Children’s Bible, audienceAgeRange, elementary-age children]
-
A.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
D.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
E.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c5f0948190b4ea729693d8c306 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.