Triple
T35458585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedwig Jankowski |
E1024848
|
entity |
| Predicate | hasFamilyProperty |
P195913
|
FINISHED |
| Object | Jankowski family farm |
—
|
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: Jankowski family farm | Statement: [Hedwig Jankowski, hasFamilyProperty, Jankowski family farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyProperty Context triple: [Hedwig Jankowski, hasFamilyProperty, Jankowski family farm]
-
A.
hasFamilyPropertyState
Indicates that a family or household possesses a particular legal or ownership status regarding a property.
-
B.
hasFamilyTrait
Indicates that a particular trait or characteristic is shared among members of the same family or lineage.
-
C.
hasFamilyPropertyCountry
Indicates that a family’s property is located in or associated with a particular country.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
hasFamilyDynamic
Indicates the type or nature of the interpersonal relationships and interaction patterns that exist within a family unit.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69fdee75d1408190bba58a9cef200a54 |
completed | May 8, 2026, 2:08 p.m. |
Created at: May 3, 2026, 4:04 p.m.