Triple

T37409669
Position Surface form Disambiguated ID Type / Status
Subject Jun-fan E929526 entity
Predicate hasBearerNotability P156150 FINISHED
Object cultural icon 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: cultural icon | Statement: [Jun-fan, hasBearerNotability, cultural icon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBearerNotability
Context triple: [Jun-fan, hasBearerNotability, cultural icon]
  • A. hasNotableBearer
    Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
  • B. hasNotabilityFor chosen
    Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
  • C. hasNotableBearerStyle
    Indicates that a particular style, form, or variant is notably associated with a specific bearer (such as a person, group, or entity) as a distinguishing characteristic.
  • D. hasNotabilityBasis
    Indicates that the notability or significance of one entity is based on, or derived from, another entity or factor.
  • E. hasNotableBearerAchievementContext
    Indicates that a notable bearer of something (such as a name, title, or identifier) is associated with a specific context in which their achievement or distinction is recognized.
  • 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_69f76ebde49481908566cd96b37ccc84 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd4129a8848190a5002150278ac689 completed May 8, 2026, 1:49 a.m.
PD Predicate disambiguation batch_69fd3e0515ec8190937c7af71ebc3875 completed May 8, 2026, 1:36 a.m.
Created at: May 3, 2026, 4:16 p.m.