Triple
T7135326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacek Kuroń |
E166292
|
entity |
| Predicate | servedInOfficeTo |
P75047
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Jacek Kuroń, servedInOfficeTo, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedInOfficeTo Context triple: [Jacek Kuroń, servedInOfficeTo, 1990]
-
A.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
B.
succeededInOffice
Indicates that one officeholder directly followed another in holding the same official position.
-
C.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
-
D.
officeHoldersServeIn
Indicates that certain office holders perform their official duties or occupy their roles within a specified office, institution, or jurisdiction.
-
E.
officeHolderServedUnder
Indicates that a person holding an office served in that role under the authority, administration, or leadership of another specified office holder or leader.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e690f954819084b81a555f4cdb5e |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:45 p.m.