Triple
T25243651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikuláš |
E632536
|
entity |
| Predicate | traditionalCompanion |
P22642
|
FINISHED |
| Object | angel |
—
|
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: angel | Statement: [Mikuláš, traditionalCompanion, angel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCompanion Context triple: [Mikuláš, traditionalCompanion, angel]
-
A.
companionOf
chosen
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
companionsCategory
Indicates that one entity is classified under a specific category related to companions or companionship.
-
C.
traditionalAncestor
Indicates that one entity is regarded as an ancestor of another according to traditional, customary, or culturally transmitted lineage beliefs rather than strictly documented genealogical records.
-
D.
traditionalHeir
Indicates that one entity is recognized as the customary or culturally designated inheritor or successor of another entity.
-
E.
traditionalSee
Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:10 p.m.