Triple

T32964660
Position Surface form Disambiguated ID Type / Status
Subject AfA E843335 entity
Predicate representsInterestGroup P149048 FINISHED
Object dependent employees 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: dependent employees | Statement: [AfA, representsInterestGroup, dependent employees]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: representsInterestGroup
Context triple: [AfA, representsInterestGroup, dependent employees]
  • A. representsInterestOf
    Indicates that one entity expresses, holds, or embodies an interest, concern, or stake in another entity or subject.
  • B. hasSpecialInterestGroup
    Indicates that an entity is associated with, supported by, or represented by a particular special interest group.
  • C. representsOwnershipInterestIn
    Indicates that one entity holds an ownership stake, share, or equity interest in another entity.
  • D. partyRepresentsInterestsOf chosen
    Indicates that one party acts to advocate for, protect, or advance the interests, needs, or goals of another party.
  • E. hasRepresentativeGroup
    Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
  • 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_69f3494af2808190ad98cec2f1bc0fe6 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fed48d8e148190a99c0aea29f8a3ee completed May 9, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fed3c82a24819095e614e31ac0307f completed May 9, 2026, 6:27 a.m.
Created at: May 1, 2026, 1:21 a.m.