Triple
T34731104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish historiography |
E1001212
|
entity |
| Predicate | important20thCenturyHistorian |
P94236
|
FINISHED |
| Object | Oskar Halecki |
—
|
NE NERFINISHED |
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: Oskar Halecki | Statement: [Polish historiography, important20thCenturyHistorian, Oskar Halecki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: important20thCenturyHistorian Context triple: [Polish historiography, important20thCenturyHistorian, Oskar Halecki]
-
A.
functionDuring20thCentury
Indicates that the function, role, or operation of one entity with respect to another occurred at some time during the 20th century.
-
B.
statusIn20thCentury
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
C.
centuryOfGreatestInfluence
Indicates the century during which an entity exerted its greatest impact or influence.
-
D.
lostCentury
Indicates that a particular century or era has been forgotten, obscured, or is missing from records or collective knowledge.
-
E.
notableFromCentury
chosen
Indicates that an entity is notably associated with, or best known from, a particular century.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.