Triple
T34560382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugenhagen |
E887319
|
entity |
| Predicate | hasKnowledgeSource |
P157114
|
FINISHED |
| Object | ancient texts |
—
|
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: ancient texts | Statement: [Bugenhagen, hasKnowledgeSource, ancient texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKnowledgeSource Context triple: [Bugenhagen, hasKnowledgeSource, ancient texts]
-
A.
knowledgeSource
chosen
Indicates that one entity serves as the origin, provider, or reference of information or understanding for another entity.
-
B.
knowledgeSourceInUniverse
Indicates that a particular source or repository of knowledge exists or is valid within a specified universe or contextual domain.
-
C.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
D.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
E.
usesKnowledgeBase
Indicates that an entity consults or relies on a structured knowledge base as a source of information to perform its actions or make decisions.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72062ad8081909e0a746d7e1734ee |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.