Triple
T36134647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rommely family |
E1045129
|
entity |
| Predicate | languageBackground |
P151
|
FINISHED |
| Object | German-speaking |
—
|
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: German-speaking | Statement: [Rommely family, languageBackground, German-speaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageBackground Context triple: [Rommely family, languageBackground, German-speaking]
-
A.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
-
B.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
C.
nativeLanguage
chosen
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
languageBranchOfDialectSpoken
Indicates that one language branch is the higher-level linguistic group from which a given spoken dialect originates or to which that dialect belongs.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 3, 2026, 4:08 p.m.