Triple

T8945935
Position Surface form Disambiguated ID Type / Status
Subject Aldershot Town F.C. E213220 entity
Predicate reasonForPhoenixSymbol P7885 FINISHED
Object reformed after Aldershot F.C. liquidation 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: reformed after Aldershot F.C. liquidation | Statement: [Aldershot Town F.C., reasonForPhoenixSymbol, reformed after Aldershot F.C. liquidation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForPhoenixSymbol
Context triple: [Aldershot Town F.C., reasonForPhoenixSymbol, reformed after Aldershot F.C. liquidation]
  • A. emblemSymbolism
    Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
  • B. shapeSymbolism
    Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
  • C. fireSymbolizes
    Indicates that the concept or element of fire is used to represent, signify, or stand for another idea, quality, or meaning in a symbolic way.
  • D. symbolOnInsignia
    Indicates that a particular symbol appears on or is featured as part of an insignia.
  • E. reasonForName chosen
    Indicates the explanation or cause behind why an entity has a particular name.
  • 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_69ca839843408190a39069a029a89f15 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66dd00c481908ff20fd66c1954cc completed April 1, 2026, 12:29 a.m.
PD Predicate disambiguation batch_69cc5ed5267c8190a43feb2a2f3df1ec completed March 31, 2026, 11:55 p.m.
Created at: March 30, 2026, 6:59 p.m.