Triple
T36127294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Meminger family (foster arrangement) |
E1044916
|
entity |
| Predicate | includesResident |
P194846
|
FINISHED |
| Object | Hans Hubermann |
E322818
|
NE 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: Hans Hubermann | Statement: [The Meminger family (foster arrangement), includesResident, Hans Hubermann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesResident Context triple: [The Meminger family (foster arrangement), includesResident, Hans Hubermann]
-
A.
includesResidence
chosen
Indicates that one entity encompasses, contains, or has within it the residence or dwelling place of another entity.
-
B.
hasTypicalResident
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
-
C.
appliesToResidentsOf
Indicates that something (such as a rule, policy, condition, or benefit) is applicable specifically to people who reside in a particular place or jurisdiction.
-
D.
hasResidentUnit
Indicates that a location or facility contains or is associated with a specific residential unit.
-
E.
coResident
Indicates that two or more entities live in the same residence or dwelling at the same time.
- F. None of above.
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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d6a0ee48190a3b3f6023de7f8f2 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.