Triple
T6272383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pax optima rerum |
E140566
|
entity |
| Predicate | hasLiteralTranslation |
P2303
|
FINISHED |
| Object | Peace, the best of things |
—
|
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: Peace, the best of things | Statement: [Pax optima rerum, hasLiteralTranslation, Peace, the best of things]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiteralTranslation Context triple: [Pax optima rerum, hasLiteralTranslation, Peace, the best of things]
-
A.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
B.
hasTranslation
chosen
Indicates that one entity is a translation or translated version of another entity in a different language.
-
C.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
-
D.
hasWorkTranslatedInto
Indicates that a work has been translated into a specified language or target work.
-
E.
laterTranslatedAs
Indicates that something was translated at a later time into a different language, form, or version under a specified title or expression.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063bca5488190b9da3c037cfc7953 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.