Triple
T1799167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feynman family archives |
E39673
|
entity |
| Predicate | chronologicallyCovers |
P32028
|
FINISHED |
| Object | life of Richard Feynman |
—
|
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: life of Richard Feynman | Statement: [Feynman family archives, chronologicallyCovers, life of Richard Feynman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyCovers Context triple: [Feynman family archives, chronologicallyCovers, life of Richard Feynman]
-
A.
chronologicallyClassifiedAs
Indicates that something is assigned to or placed within a specific time period or chronological category.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
D.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
-
E.
chronologyNextTitle
Indicates that one item is immediately followed by another item as the next title in a chronological sequence.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab61b5c8988190bb2b46182a4eb5b4 |
completed | March 6, 2026, 11:22 p.m. |
Created at: March 4, 2026, 7:32 p.m.