Triple
T25737765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georg Baresch |
E648121
|
entity |
| Predicate | sentManuscriptCopiesTo |
P36417
|
FINISHED |
| Object | Athanasius Kircher |
—
|
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: Athanasius Kircher | Statement: [Georg Baresch, sentManuscriptCopiesTo, Athanasius Kircher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentManuscriptCopiesTo Context triple: [Georg Baresch, sentManuscriptCopiesTo, Athanasius Kircher]
-
A.
copiedManuscriptsOf
Indicates that one entity has produced or created handwritten reproductions of the manuscripts belonging to another entity.
-
B.
hasManuscriptsIn
Indicates that an entity possesses or is associated with manuscripts that are located in a specified place or collection.
-
C.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
-
D.
sentDocumentTo
chosen
Indicates that one entity transmitted or delivered a document to another entity.
-
E.
sharesManuscriptWith
Indicates that one party provides or grants access to a manuscript to another party.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1726708190ab4382bf35e2db90 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:36 a.m.