Triple
T16952136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim McDermott |
E411206
|
entity |
| Predicate | notableOfficeStart |
P73495
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Jim McDermott, notableOfficeStart, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOfficeStart Context triple: [Jim McDermott, notableOfficeStart, 1989]
-
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.
notableOfficeStatus
Indicates that an entity holds or has held a particularly significant or distinguished official position or office.
-
C.
officeStartFor
chosen
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
-
D.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
-
E.
notableOfficer
Indicates that an entity has served as a significant or distinguished officer of another entity, such as an organization, institution, or group.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.