Triple
T22674778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADAAA |
E560317
|
entity |
| Predicate | majorLifeActivitiesExamples |
P149193
|
FINISHED |
| Object | caring for oneself |
—
|
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: caring for oneself | Statement: [ADAAA, majorLifeActivitiesExamples, caring for oneself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLifeActivitiesExamples Context triple: [ADAAA, majorLifeActivitiesExamples, caring for oneself]
-
A.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
C.
possibleFieldOfActivity
Indicates that something is a potential or suitable area in which an entity can operate, work, or be active.
-
D.
activitiesCarriedOutFor
Indicates that certain activities are performed on behalf of, in service of, or for the benefit of a particular entity.
-
E.
roleInIndividualLife
Indicates the specific function, influence, or involvement that one entity has within the personal life or experiences of another entity.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178229e908190b696d14a93c11344 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:10 p.m.