Triple
T32784238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Gladney |
E838443
|
entity |
| Predicate | lifeEventDocumentedBy |
P87206
|
FINISHED |
| Object | Isabel Wilkerson |
—
|
NE NERFINISHED |
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: Isabel Wilkerson | Statement: [George Gladney, lifeEventDocumentedBy, Isabel Wilkerson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeEventDocumentedBy Context triple: [George Gladney, lifeEventDocumentedBy, Isabel Wilkerson]
-
A.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
-
B.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
C.
significantEventDocumented
chosen
Indicates that a notable or impactful event has been formally recorded or documented in some medium.
-
D.
settingOfLifeEvents
Indicates the location or environment in which significant life events of an entity take place.
-
E.
lifeCycleEvent
Indicates an event or transition occurring at a particular stage within an entity's overall life cycle.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.