Triple

T1398645
Position Surface form Disambiguated ID Type / Status
Subject Service Committee E30727 entity
Predicate worksTo P27740 FINISHED
Object support the expansion of evangelizing work 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: support the expansion of evangelizing work | Statement: [Service Committee, worksTo, support the expansion of evangelizing work]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: worksTo
Context triple: [Service Committee, worksTo, support the expansion of evangelizing work]
  • A. workBy
    Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
  • B. worksFor
    Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
  • C. worksOver
    Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
  • D. worksWith
    Indicates that two entities collaborate or perform tasks together in a shared work-related context.
  • E. worksThrough
    Indicates that one entity performs an action, causes an effect, or achieves a result by using, employing, or acting via another entity as an intermediary or means.
  • 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_69a498fd4e408190bd73eca30ea9754c completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c382b6588190833c39ac84fb6139 completed March 1, 2026, 10:53 p.m.
PD Predicate disambiguation batch_69a4bf017f8081908572121560ec621f completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4c13270d8819081d8ee1be34cabf5 completed March 1, 2026, 10:44 p.m.
Created at: March 1, 2026, 7:59 p.m.