Triple

T6385233
Position Surface form Disambiguated ID Type / Status
Subject Frisch elasticity of labor supply E143682 entity
Predicate estimatedUsing P70307 FINISHED
Object micro data on hours and wages 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: micro data on hours and wages | Statement: [Frisch elasticity of labor supply, estimatedUsing, micro data on hours and wages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: estimatedUsing
Context triple: [Frisch elasticity of labor supply, estimatedUsing, micro data on hours and wages]
  • A. areEstimatedIn
    Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
  • B. estimatedCost
    Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
  • C. approximates
    Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
  • D. approximateEndUse
    Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
  • E. actualUse
    Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
  • 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_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.
PDg Predicate description generation batch_69c0623d23448190a75cf5d802fc0a02 completed March 22, 2026, 9:42 p.m.
Created at: March 22, 2026, 4:34 p.m.