Triple

T33362219
Position Surface form Disambiguated ID Type / Status
Subject E854251 entity
Predicate usedAsGivenNameComponent P70064 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: [錢, usedAsGivenNameComponent, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedAsGivenNameComponent
Context triple: [錢, usedAsGivenNameComponent, yes]
  • A. hasGivenNames
    Indicates that an entity possesses one or more personal (given) names assigned to it.
  • B. canBeGivenNameOnItsOwn chosen
    Indicates that something is acceptable or valid to be used as a standalone given name without needing additional components.
  • C. selfGivenName
    Indicates that an entity has a particular given (first) name assigned to itself.
  • D. isGivenName
    Indicates that one entity is the personal (given) name of another entity.
  • E. usedAsSurname
    Indicates that something functions as a family name borne by a person or group of people.
  • 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_69f3496bda8c8190bfc8fade9d1b791c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fdec5ffe088190ac5505f26c6cff18 completed May 8, 2026, 2 p.m.
PD Predicate disambiguation batch_69fdeae15f1c81908fc63fbc1b028d2e completed May 8, 2026, 1:53 p.m.
Created at: May 1, 2026, 1:34 a.m.