Triple

T2637161
Position Surface form Disambiguated ID Type / Status
Subject Britannia E59771 entity
Predicate revivedAsSymbol P9802 FINISHED
Object late 17th century 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: late 17th century | Statement: [Britannia, revivedAsSymbol, late 17th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: revivedAsSymbol
Context triple: [Britannia, revivedAsSymbol, late 17th century]
  • A. revivedBy
    Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
  • B. revival chosen
    Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
  • C. reconstructedAs
    Indicates that one entity has been rebuilt, recreated, or inferred based on evidence, models, or partial information from another entity.
  • D. focusDuringRevival
    Indicates that one entity maintains or directs focused attention on another entity or process during a revival event or restoration phase.
  • E. reintroducedFrom
    Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
  • 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_69ab4ac8596c8190b34997e73d9e991c completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd8e3190081908ea828fe79569cc9 completed March 7, 2026, 7:50 a.m.
PD Predicate disambiguation batch_69abd812849881908f956845a80e0205 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:50 p.m.