Triple
T9194510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verfall einer Familie |
E220669
|
entity |
| Predicate | usedAsMarketingTitleIn |
P86932
|
FINISHED |
| Object | German-speaking countries |
—
|
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 countries | Statement: [Verfall einer Familie, usedAsMarketingTitleIn, German-speaking countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMarketingTitleIn Context triple: [Verfall einer Familie, usedAsMarketingTitleIn, German-speaking countries]
-
A.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
B.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
C.
usedAsTitleUntil
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
D.
usedAsWorkingTitleDuring
Indicates that one title temporarily served as the working or provisional title of a work during a specified time period.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c3614c81909e26417e00fdfa11 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6745c17881908df72443e0800068 |
completed | April 1, 2026, 12:31 a.m. |
Created at: March 30, 2026, 7:25 p.m.