Triple
T33388962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabdeno |
E854993
|
entity |
| Predicate | indicatedInAgeGroup |
P125218
|
FINISHED |
| Object | individuals 1 year of age and older |
—
|
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: individuals 1 year of age and older | Statement: [Zabdeno, indicatedInAgeGroup, individuals 1 year of age and older]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatedInAgeGroup Context triple: [Zabdeno, indicatedInAgeGroup, individuals 1 year of age and older]
-
A.
ageGroupIndicated
chosen
Indicates that a specific age range or category is identified or assigned to an entity.
-
B.
intendedForAgeGroup
Indicates that something is designed, suitable, or targeted for use by a specific age group.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
supportsAgeRange
Indicates that one entity is compatible with, valid for, or designed to accommodate a specified range of ages.
-
E.
performedForAgeGroup
Indicates that an action or performance is specifically intended for, targeted at, or carried out on behalf of a particular age group.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:35 a.m.