Triple
T23118884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacem, Veritatem, Creatio |
E576833
|
entity |
| Predicate | translatedConcept |
P82717
|
FINISHED |
| Object | peace |
—
|
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 | Statement: [Pacem, Veritatem, Creatio, translatedConcept, peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translatedConcept Context triple: [Pacem, Veritatem, Creatio, translatedConcept, peace]
-
A.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
B.
translatedSection
Indicates that one text section is a translation of another corresponding section in a different language or version.
-
C.
translationApproximate
Indicates that one entity is an inexact or approximate translation of another, preserving general meaning but not precise wording or full detail.
-
D.
translationHint
Indicates that one entity provides guidance or suggestions on how another entity should be translated into a different language.
-
E.
translationProperty
chosen
Indicates a relationship where one entity serves as a translated counterpart or translation-specific attribute of another 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e4ece5481908d05b4b1e6a07db3 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.