Triple
T29441209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan |
E746715
|
entity |
| Predicate | commonInLanguageFamily |
P192770
|
FINISHED |
| Object | Germanic languages |
—
|
NE NERFINISHED |
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: [Jan, commonInLanguageFamily, Germanic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInLanguageFamily Context triple: [Jan, commonInLanguageFamily, Germanic languages]
-
A.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
B.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
C.
basedOnLanguageFamily
Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
-
D.
areOfficialLanguageFamilyOf
Indicates that one or more language families hold official status within, or are formally recognized as official for, a particular entity (such as a country or region).
-
E.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, a particular language 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: April 28, 2026, 3:22 p.m.