Triple
T32729885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In varietate concordia |
E836918
|
entity |
| Predicate | translationOfWord_varietate |
P184453
|
FINISHED |
| Object | diversity |
—
|
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: diversity | Statement: [In varietate concordia, translationOfWord_varietate, diversity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationOfWord_varietate Context triple: [In varietate concordia, translationOfWord_varietate, diversity]
-
A.
referenceVarietyFor
Indicates that one entity is used as the standard or benchmark variety against which another entity is referenced or compared.
-
B.
isTranslationVariantOf
chosen
Indicates that one expression is a different linguistic rendering or version of the same content as another expression, typically across languages or translation forms.
-
C.
tipoDeVariedadDescrita
Indicates that one entity specifies or denotes the type of variety described for another entity.
-
D.
languageVariants
Indicates that one language form is a variant or alternative version of another language.
-
E.
languageOfWord
Indicates that a particular language is the one in which a given word is expressed or defined.
- 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_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1:11 a.m.