Triple
T32278299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De generatione animalium |
E824618
|
entity |
| Predicate | hasModernLanguageTranslations |
P2303
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [De generatione animalium, hasModernLanguageTranslations, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernLanguageTranslations Context triple: [De generatione animalium, hasModernLanguageTranslations, Latin]
-
A.
hasModernNameLanguage
Indicates that the modern name of an entity is expressed in a particular language.
-
B.
hasTranslation
chosen
Indicates that one entity is a translation or translated version of another entity in a different language.
-
C.
hasTraditionalTranslation
Indicates that one entity serves as the established or customary translation of another entity in a traditional or historically accepted sense.
-
D.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
E.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 1, 2026, 12:43 a.m.