Triple
T32742659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revelge |
E837257
|
entity |
| Predicate | textCollectionEditors |
P144369
|
FINISHED |
| Object | Achim von Arnim |
—
|
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: Achim von Arnim | Statement: [Revelge, textCollectionEditors, Achim von Arnim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textCollectionEditors Context triple: [Revelge, textCollectionEditors, Achim von Arnim]
-
A.
textCollectionSource
Indicates that a text collection originates from, or is derived from, a particular source.
-
B.
editorCommunity
Indicates a relationship where an editor is associated with, participates in, or belongs to a particular community.
-
C.
hasCollectionEditor
chosen
Indicates that an entity serves as the editor responsible for curating, managing, or overseeing a particular collection.
-
D.
coEditor
Indicates that two or more entities share responsibility for editing the same work or publication.
-
E.
editorName
Indicates the relationship that specifies the name of an editor associated with a given entity.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:12 a.m.