Triple
T26981949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alingsås Cemetery |
E679624
|
entity |
| Predicate | hasNotableWriterBuried |
P10455
|
FINISHED |
| Object | Karin Boye |
—
|
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: Karin Boye | Statement: [Alingsås Cemetery, hasNotableWriterBuried, Karin Boye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWriterBuried Context triple: [Alingsås Cemetery, hasNotableWriterBuried, Karin Boye]
-
A.
hasNotableWriter
chosen
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
-
B.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
-
C.
hasNotableExpositor
Indicates that an entity has a person or source that is especially recognized for explaining, interpreting, or presenting it.
-
D.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
E.
hasWriterOfWork
Indicates that a person or entity is the writer/author who created a particular work (such as a book, article, or script).
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 27, 2026, 6:46 a.m.