Triple
T34351364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Aldrich |
E881585
|
entity |
| Predicate | assumedSeniorStatusOn |
P120098
|
FINISHED |
| Object | 1995-07-01 |
—
|
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: 1995-07-01 | Statement: [Ann Aldrich, assumedSeniorStatusOn, 1995-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumedSeniorStatusOn Context triple: [Ann Aldrich, assumedSeniorStatusOn, 1995-07-01]
-
A.
dateOfTakingSeniorStatus
chosen
Indicates the date on which an individual assumed senior status in a role, typically marking a transition from full active service to a reduced or semi-retired capacity.
-
B.
isSeniorTo
Indicates that one entity holds a higher rank, status, or level of authority than another.
-
C.
isElderly
Indicates that an entity is of advanced age, typically considered old within its relevant context.
-
D.
hasSeniorityStatus
Indicates that one entity holds a particular level or classification of seniority relative to others.
-
E.
appliesToRetirementStatus
Indicates that the subject is relevant or applicable specifically to an entity’s retirement status or condition.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:58 a.m.