Triple
T5506829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Benchley |
E144459
|
entity |
| Predicate | notableFamilyActivity |
P65137
|
FINISHED |
| Object | writing |
—
|
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: writing | Statement: [Christopher Benchley, notableFamilyActivity, writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyActivity Context triple: [Christopher Benchley, notableFamilyActivity, writing]
-
A.
familyEvent
Indicates a relationship where an event is organized around or significantly involves members of a family, such as gatherings, celebrations, or milestones.
-
B.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
C.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
D.
notableRoutine
Indicates a routine, practice, or sequence of actions that is especially prominent, well-known, or significant in some context.
-
E.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f47d2dc8190ad874be6902d8a4c |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:32 p.m.