Triple

T10825962
Position Surface form Disambiguated ID Type / Status
Subject python-dev mailing list E255497 entity
Predicate archiveAvailability P95938 FINISHED
Object public web archives 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: public web archives | Statement: [python-dev mailing list, archiveAvailability, public web archives]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: archiveAvailability
Context triple: [python-dev mailing list, archiveAvailability, public web archives]
  • A. archivesStatus
    Indicates the current archival state or condition assigned to an item, such as whether it is archived, active, or pending archiving.
  • B. archivesHeldBy
    Indicates that archival materials or records are kept, managed, or preserved by a particular entity.
  • C. archivesHeldIn
    Indicates that archival materials or records are stored, maintained, or preserved at a specified location or institution.
  • D. archiveContent
    Indicates that content is being stored or moved into an archive state for long-term retention or historical reference.
  • E. archivesType
    Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
  • 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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d734d1c24881909f56d56207cccbef completed April 9, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69d70d1bf3648190b36fa96ea018e0dc completed April 9, 2026, 2:21 a.m.
PDg Predicate description generation batch_69d7101c96708190808fef73199e8482 completed April 9, 2026, 2:34 a.m.
Created at: April 8, 2026, 9:19 p.m.