Triple
T35176730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nils Bjurman |
E1015725
|
entity |
| Predicate | replacesAsGuardian |
P118420
|
FINISHED |
| Object | Holger Palmgren |
—
|
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: Holger Palmgren | Statement: [Nils Bjurman, replacesAsGuardian, Holger Palmgren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesAsGuardian Context triple: [Nils Bjurman, replacesAsGuardian, Holger Palmgren]
-
A.
guardianAppointedFor
chosen
Indicates that one entity has been formally designated as the legal guardian responsible for another entity.
-
B.
roleReplacedOn
Indicates that one role has been substituted or taken over by another role at a specific point in time.
-
C.
adoptiveParent
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
D.
replacedByInLawEnforcement
Indicates that one entity has been superseded or taken over by another entity within a law enforcement context, such as in role, function, or authority.
-
E.
appointedInCapacityOf
Indicates that an entity is appointed to a role, position, or task specifically in a defined capacity or function.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:02 p.m.