Triple
T14965430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European bourgeoisie |
E373176
|
entity |
| Predicate | hasTypicalLifestyle |
P51691
|
FINISHED |
| Object | urban residence |
—
|
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: urban residence | Statement: [European bourgeoisie, hasTypicalLifestyle, urban residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalLifestyle Context triple: [European bourgeoisie, hasTypicalLifestyle, urban residence]
-
A.
supportsLifestyle
Indicates that one entity provides the resources, conditions, or assistance necessary for another entity to maintain a particular way of living.
-
B.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
typicallyLack
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
-
D.
typicalGoing
Indicates that an entity is engaged in or undergoing a normal, expected instance of going or movement from one place to another.
-
E.
lifeHabit
chosen
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.
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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e2fdcc8190bffe603db3388736 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:47 a.m.