Triple
T5853227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry J. Friendly |
E130086
|
entity |
| Predicate | tookSeniorStatus |
P31749
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Henry J. Friendly, tookSeniorStatus, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookSeniorStatus Context triple: [Henry J. Friendly, tookSeniorStatus, 1974]
-
A.
turnedSenior
chosen
Indicates that an entity has transitioned into senior status or a senior role relative to a previous state or position.
-
B.
isSeniorTo
Indicates that one entity holds a higher rank, status, or level of authority than another.
-
C.
hasPermanentSeniority
Indicates that one entity holds a fixed, enduring precedence or higher rank over another that does not change over time.
-
D.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
-
E.
isTenuredPosition
Indicates that a position is a permanent academic or professional role typically protected from arbitrary dismissal.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.