Triple
T2585665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Chancery |
E57991
|
entity |
| Predicate | settingClass |
P40532
|
FINISHED |
| Object | upper-middle class |
—
|
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: upper-middle class | Statement: [In Chancery, settingClass, upper-middle class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingClass Context triple: [In Chancery, settingClass, upper-middle class]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
settingCategory
Indicates the classification or type of context in which something is set or configured (e.g., grouping settings under a common category).
-
C.
supportedClass
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
D.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
E.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3cd07588190b3cb8cc348f12938 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd37ef248819090ab6b86b67e355f |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.