Triple
T32729886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In varietate concordia |
E836918
|
entity |
| Predicate | translationOfWord_concordia |
P52481
|
FINISHED |
| Object | harmony |
—
|
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: harmony | Statement: [In varietate concordia, translationOfWord_concordia, harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationOfWord_concordia Context triple: [In varietate concordia, translationOfWord_concordia, harmony]
-
A.
translatedWorkOf
Indicates that one work is a translation of another original work.
-
B.
translationOn
chosen
Indicates that one entity is a translation of another entity, typically expressing the same content in a different language or linguistic form.
-
C.
translationProperty
Indicates a relationship where one entity serves as a translated counterpart or translation-specific attribute of another entity.
-
D.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
E.
translationApproximate
Indicates that one entity is an inexact or approximate translation of another, preserving general meaning but not precise wording or full detail.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 1, 2026, 1:11 a.m.