Triple
T33758768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alf |
E865048
|
entity |
| Predicate | derivesFromLanguageFamily |
P30710
|
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: [Alf, derivesFromLanguageFamily, Germanic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesFromLanguageFamily Context triple: [Alf, derivesFromLanguageFamily, Germanic languages]
-
A.
derivedFromLanguageFamily
chosen
Indicates that one language originates from, or historically descends from, a particular language family.
-
B.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
C.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
D.
basedOnLanguageFamily
Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
-
E.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.