Triple
T14146235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwinne |
E350556
|
entity |
| Predicate | relatedToOnomastics |
P111023
|
FINISHED |
| Object | medieval personal names |
—
|
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: medieval personal names | Statement: [Baldwinne, relatedToOnomastics, medieval personal names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToOnomastics Context triple: [Baldwinne, relatedToOnomastics, medieval personal names]
-
A.
commonInOnomastics
Indicates that a name, term, or pattern frequently appears or is widely used within the study and practice of naming (onomastics).
-
B.
relatedToTerm
chosen
Indicates a general, non-specific relationship or association between one term and another.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
relatedNamedEntity
Indicates that two entities are connected through a shared or associated proper name (e.g., person, organization, location, or other named entity).
-
E.
relatedPaliName
Indicates that one entity has an associated or corresponding name expressed in Pali for the other 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de612266248190a8591b646fe30ae6 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:54 a.m.