Triple

T8998370
Position Surface form Disambiguated ID Type / Status
Subject Aurora E214975 entity
Predicate hasHistoricalArc P85600 FINISHED
Object decline leading to abandonment 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: decline leading to abandonment | Statement: [Aurora, hasHistoricalArc, decline leading to abandonment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalArc
Context triple: [Aurora, hasHistoricalArc, decline leading to abandonment]
  • A. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • B. hasHistoricalPrecursor
    Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
  • C. hasHistoryPeriod
    Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
  • D. hasHistoricalRoute
    Indicates that an entity possesses or is associated with a route that has historical significance or origin.
  • E. hasHistorySince
    Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
  • 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_69ca83a12d648190b1e4fe11e8a31890 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc68e23734819083a98f4ff0942479 completed April 1, 2026, 12:37 a.m.
PD Predicate disambiguation batch_69cc5edd6cb48190b4fc6d6ca0418056 completed March 31, 2026, 11:55 p.m.
PDg Predicate description generation batch_69cc5f6dec4081909379bd57c02a5710 completed March 31, 2026, 11:57 p.m.
Created at: March 30, 2026, 7:05 p.m.