Triple
T30940914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sababurg Castle |
E788257
|
entity |
| Predicate | associatedWithAuthors |
P36711
|
FINISHED |
| Object | Brothers Grimm |
E1103850
|
NE 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: Brothers Grimm | Statement: [Sababurg Castle, associatedWithAuthors, Brothers Grimm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAuthors Context triple: [Sababurg Castle, associatedWithAuthors, Brothers Grimm]
-
A.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
B.
associatedWithAuthorRole
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
C.
associatedWithAuthorType
Indicates that one entity has a specified type of association or role in relation to an author.
-
D.
placeAssociatedWithAuthor
chosen
Indicates a relationship where a place is connected to an author, such as by birth, residence, work, or significant activity.
-
E.
associatedWithAuthorConcern
Indicates a relationship where something is linked to, influenced by, or arises from an author’s specific concern, issue, or point of focus.
- F. None of above.
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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35afafbd408190a29c4d5259bcbd9e |
completed | June 19, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:53 p.m.