Triple
T21875487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lulu Bett |
E540130
|
entity |
| Predicate | lifeSituation |
P146005
|
FINISHED |
| Object | constrained domestic life |
—
|
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: constrained domestic life | Statement: [Lulu Bett, lifeSituation, constrained domestic life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeSituation Context triple: [Lulu Bett, lifeSituation, constrained domestic life]
-
A.
living
Indicates that an entity is alive or currently exists in a living state.
-
B.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
C.
livelihood
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
D.
settingOfLifeEvents
Indicates the location or environment in which significant life events of an entity take place.
-
E.
lifeHabit
Indicates the typical way an organism lives or behaves in its environment, such as its mode of life, activity pattern, or ecological lifestyle.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33957f481908789b054a4fd1b77 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:02 p.m.