Triple
T6385201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisch elasticity of labor supply |
E143682
|
entity |
| Predicate | holdsConstant |
P3644
|
FINISHED |
| Object | expected lifetime wealth |
—
|
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: expected lifetime wealth | Statement: [Frisch elasticity of labor supply, holdsConstant, expected lifetime wealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsConstant Context triple: [Frisch elasticity of labor supply, holdsConstant, expected lifetime wealth]
-
A.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
-
B.
constant
chosen
Indicates that the relationship or value does not change across different instances, contexts, or over time.
-
C.
includesConstant
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
D.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
E.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686764648190864163d390db292d |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.