Triple
T25711543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevil Senior |
E644744
|
entity |
| Predicate | workFirstPerformedIn |
P159799
|
FINISHED |
| Object | 1722 |
—
|
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: 1722 | Statement: [Bevil Senior, workFirstPerformedIn, 1722]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFirstPerformedIn Context triple: [Bevil Senior, workFirstPerformedIn, 1722]
-
A.
workedPrimarilyOn
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
-
B.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
-
C.
initiallyWorksFor
Indicates that an entity’s first or original employment or working relationship is with a specified organization or employer.
-
D.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc157d9c819096b30f09438e351a |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 9:14 p.m.