Triple

T11871322
Position Surface form Disambiguated ID Type / Status
Subject Chángzhēng E282412 entity
Predicate isUsedInHistoricalWriting P16500 FINISHED
Object yes 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: yes | Statement: [Chángzhēng, isUsedInHistoricalWriting, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isUsedInHistoricalWriting
Context triple: [Chángzhēng, isUsedInHistoricalWriting, yes]
  • A. hasHistoriographicalUse chosen
    Indicates that something is used or cited within historical writing or analysis as part of constructing, interpreting, or debating historical narratives.
  • B. attestedInWriting
    Indicates that the relationship or fact is documented or confirmed in written form, such as in texts, records, or inscriptions.
  • C. hasWritingTraditionSince
    Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
  • D. hasHistoricalWritingInfluenceFrom
    Indicates that one entity’s historical writing style, content, or traditions are influenced by those of another entity.
  • E. hasWritingTraditionVia
    Indicates that an entity possesses or participates in a writing tradition by means of, or through the mediation of, another specified entity or method.
  • 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_69d6ab2945d081908a5851c916cbcfb5 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8d39d2934819093b9f7006f45e5cb completed April 10, 2026, 10:40 a.m.
PD Predicate disambiguation batch_69d8bb272f88819090c37c944c5a60ab completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:43 p.m.