Triple
T1573130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludovica |
E33585
|
entity |
| Predicate | derivedFromLanguageFamily |
P30710
|
FINISHED |
| Object | Germanic languages |
—
|
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: Germanic languages | Statement: [Ludovica, derivedFromLanguageFamily, Germanic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromLanguageFamily Context triple: [Ludovica, derivedFromLanguageFamily, Germanic languages]
-
A.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
B.
influencedLanguageFamily
Indicates that one language family has had a significant impact on the development, structure, or usage of another language family.
-
C.
ancientLanguageFamily
Indicates that one language belongs to or descends from a historically ancient family of related languages.
-
D.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
E.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
- F. None of above. chosen
Provenance (4 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:27 p.m.