Triple
T35186045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernie Bushmiller |
E1015985
|
entity |
| Predicate | startOfWorkOnNancy |
P125053
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Ernie Bushmiller, startOfWorkOnNancy, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfWorkOnNancy Context triple: [Ernie Bushmiller, startOfWorkOnNancy, 1933]
-
A.
startOfWork
chosen
Indicates the point in time or event at which a work activity, project, or task begins.
-
B.
startedNear
Indicates that one event or action began close in time or space to another event or action.
-
C.
namedForWorkOn
Indicates that an entity is named in honor of another entity specifically because of that entity’s work or contributions in a particular field or endeavor.
-
D.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
E.
collaborationStartWork
Indicates the point in time when a collaborative effort between entities begins or is initiated.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
Created at: May 3, 2026, 4:02 p.m.