Triple
T23046721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anonymous monk of Lindisfarne |
E573895
|
entity |
| Predicate | anonymity |
P150779
|
FINISHED |
| Object | real name unknown |
—
|
LITERAL 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: real name unknown | Statement: [Anonymous monk of Lindisfarne, anonymity, real name unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anonymity Context triple: [Anonymous monk of Lindisfarne, anonymity, real name unknown]
-
A.
anonymityFunction
Indicates a function or mechanism that preserves or enforces anonymity in the relationship or interaction between entities.
-
B.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
C.
soughtPrivacy
Indicates that an entity intentionally attempted to obtain or maintain privacy from others.
-
D.
identityConcealedBy
Indicates that one entity hides, masks, or obscures the true identity of another entity.
-
E.
publishedAnonymously
Indicates that a work was made public without revealing the identity of its creator or author.
- F. None of above. chosen
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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18678e5c48190a96a7b4c9c82f8fe |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.