Triple
T11611717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Pension for Indigent Senior Citizens |
E275398
|
entity |
| Predicate | ageGroupCovered |
P19123
|
FINISHED |
| Object | older persons |
—
|
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: older persons | Statement: [Social Pension for Indigent Senior Citizens, ageGroupCovered, older persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageGroupCovered Context triple: [Social Pension for Indigent Senior Citizens, ageGroupCovered, older persons]
-
A.
ageGroup
chosen
Indicates the categorical age range or bracket to which an entity belongs.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
-
D.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
E.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a043a3c08190a20cbc2ba5a8d218 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.