Triple

T18531408
Position Surface form Disambiguated ID Type / Status
Subject SymfonyCon E452837 entity
Predicate hasNetworkingOpportunity P44150 FINISHED
Object community meetups 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: community meetups | Statement: [SymfonyCon, hasNetworkingOpportunity, community meetups]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNetworkingOpportunity
Context triple: [SymfonyCon, hasNetworkingOpportunity, community meetups]
  • A. networkingOpportunityFor chosen
    Indicates that one entity provides or represents a chance for another entity to make professional or social connections.
  • B. hasDevelopmentOpportunity
    Indicates that an entity offers or possesses a potential for growth, improvement, or advancement, typically in skills, performance, or capabilities.
  • C. hasNotableConnectionToWork
    Indicates that there is a significant or noteworthy relationship, influence, or association between an entity and a particular work.
  • D. hasConnectionToWork
    Indicates that one entity is linked or related to another through a work-related or professional connection.
  • E. hasOutreachComponent
    Indicates that something includes or is associated with an outreach-related element, activity, or component.
  • 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e533fd0e348190ab3d4548f74b9b79 completed April 19, 2026, 7:58 p.m.
PD Predicate disambiguation batch_69e469e0025c81908f16ed4f922674af completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 11:37 a.m.