Triple

T7893439
Position Surface form Disambiguated ID Type / Status
Subject Premium Career E183291 entity
Predicate isTailoredFor P9494 FINISHED
Object people actively looking for a new job 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: people actively looking for a new job | Statement: [Premium Career, isTailoredFor, people actively looking for a new job]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTailoredFor
Context triple: [Premium Career, isTailoredFor, people actively looking for a new job]
  • A. isSuitableFor
    Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
  • B. isDesignedFor chosen
    Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
  • C. isDesignedAs
    Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
  • D. isAbout
    Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
  • E. isBuiltFor
    Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a008fb88190a039fec40483ab93 completed March 31, 2026, 3:05 a.m.
PD Predicate disambiguation batch_69cae92b0cd881908e715a10d3252e83 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5 p.m.