Triple

T3148873
Position Surface form Disambiguated ID Type / Status
Subject Community Development Entity E65827 entity
Predicate mayBeOrganizedAs P4786 FINISHED
Object nonprofit corporation 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: nonprofit corporation | Statement: [Community Development Entity, mayBeOrganizedAs, nonprofit corporation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeOrganizedAs
Context triple: [Community Development Entity, mayBeOrganizedAs, nonprofit corporation]
  • A. organizedAs chosen
    Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
  • B. organizesInto
    Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
  • C. organisedFor
    Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
  • D. oftenOrganizedBy
    Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
  • E. notOrganizedBy
    Indicates that an event, activity, or entity is explicitly not arranged, coordinated, or managed by a specified agent or organization.
  • 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_69ad8584485081909ed529e890cadc4a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada5be30fc819097edb620c65055d5 completed March 8, 2026, 4:37 p.m.
PD Predicate disambiguation batch_69ad9dfa3d9081908425aa636bb9b897 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:05 p.m.