Triple
T2433392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Companion Program |
E52897
|
entity |
| Predicate | volunteersAgeRequirement |
P39177
|
FINISHED |
| Object | 55 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: 55 and older | Statement: [Senior Companion Program, volunteersAgeRequirement, 55 and older]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volunteersAgeRequirement Context triple: [Senior Companion Program, volunteersAgeRequirement, 55 and older]
-
A.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
B.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
C.
minimumRegistrationAge
Indicates the lowest age at which an entity is allowed or eligible to register for something.
-
D.
maximumRegistrationAge
Indicates the highest age at which an entity is allowed or eligible to register.
-
E.
militaryAge
Indicates that an entity is within the age range typically considered eligible for military service.
- F. None of above. chosen
Provenance (4 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc73d2e48190b6ad5f3ee75b74eb |
completed | March 7, 2026, 6:57 a.m. |
Created at: March 6, 2026, 9:43 p.m.