Triple
T7584911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endicott Peabody |
E179582
|
entity |
| Predicate | notableOfficeStartPeriod |
P65173
|
FINISHED |
| Object | early 1960s |
—
|
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: early 1960s | Statement: [Endicott Peabody, notableOfficeStartPeriod, early 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOfficeStartPeriod Context triple: [Endicott Peabody, notableOfficeStartPeriod, early 1960s]
-
A.
notableOfficeStartContext
Indicates the contextual circumstances or conditions (such as time, place, or situation) surrounding the beginning of a notable office or position held by an entity.
-
B.
notableOfficePeriod
chosen
Indicates that an entity held a particular office or position during a specified time period.
-
C.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
D.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
E.
firstOfficeHolderStart
Indicates the date or time when the first person to hold a particular office or position began their term.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f993cd0c8190864f801074625a32 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.