Triple
T16602385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohor |
E403361
|
entity |
| Predicate | titleLanguageMeaning |
P123495
|
FINISHED |
| Object | Bohor refers to a type of amulet or ornament |
—
|
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: Bohor refers to a type of amulet or ornament | Statement: [Bohor, titleLanguageMeaning, Bohor refers to a type of amulet or ornament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleLanguageMeaning Context triple: [Bohor, titleLanguageMeaning, Bohor refers to a type of amulet or ornament]
-
A.
titleMeaning
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
C.
nameMeaningLanguage
Indicates that a specified meaning of a name is expressed or interpreted in a particular language.
-
D.
textMeaning
Indicates that one text expresses, conveys, or corresponds to a particular meaning or semantic content.
-
E.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d770a048190be42180b03efba0b |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.