Triple

T205738
Position Surface form Disambiguated ID Type / Status
Subject Anacreon E4606 entity
Predicate reception P9965 FINISHED
Object highly admired in antiquity 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: highly admired in antiquity | Statement: [Anacreon, reception, highly admired in antiquity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reception
Context triple: [Anacreon, reception, highly admired in antiquity]
  • A. hasReception
    Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
  • B. receives
    Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
  • C. attendance
    Indicates the relationship between an event and the people who are present at or participate in that event.
  • D. venue
    Indicates the place or location where an event, activity, or interaction takes place.
  • E. reservationSystem
    Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
  • 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_69a25737567c81908f9c505300239181 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25e2aba74819093eddd8d820260c0 completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b4c7f908190876c1041db52dffc completed Feb. 28, 2026, 3:04 a.m.
PDg Predicate description generation batch_69a25e292fdc8190bfd51d8848f9ed58 completed Feb. 28, 2026, 3:16 a.m.
Created at: Feb. 28, 2026, 2:51 a.m.