Triple
T18921621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vratislav |
E462871
|
entity |
| Predicate | hasGeneralMeaning |
P3918
|
FINISHED |
| Object | one who returns glory |
—
|
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: one who returns glory | Statement: [Vratislav, hasGeneralMeaning, one who returns glory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralMeaning Context triple: [Vratislav, hasGeneralMeaning, one who returns glory]
-
A.
hasMeaningCategory
Indicates that something is associated with a particular category of meaning or semantic type.
-
B.
hasMean
Indicates that one entity possesses, exhibits, or is characterized by a particular mean value or average.
-
C.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
D.
hasLiteralMeaning
chosen
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
E.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b3b93c819085032d8251a43ca8 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.