Triple

T34535007
Position Surface form Disambiguated ID Type / Status
Subject Wellington Quay E886643 entity
Predicate namedForEventOrPersonRole P191916 FINISHED
Object British military leader and statesman 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: British military leader and statesman | Statement: [Wellington Quay, namedForEventOrPersonRole, British military leader and statesman]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: namedForEventOrPersonRole
Context triple: [Wellington Quay, namedForEventOrPersonRole, British military leader and statesman]
  • A. namedPersonRole
    Indicates that a person is identified by name as holding a specific role or position in a given context.
  • B. namedForPersonField
    Indicates that a field or area is named in honor of a specific person.
  • C. namedForPersonFullName
    Indicates that an entity is named after a specific person, identified by that person’s full name.
  • D. namedForPersonAffiliation
    Indicates that something is named after a person specifically because of that person's affiliation with a particular group, organization, place, or role.
  • E. namedForEventAssociatedWithHonoree
    Indicates that something is named in recognition of an event that is closely associated with the honoree.
  • 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_69f349ce5eb881909e431c670944aa68 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fcef654d588190b29ecc76678d1aa0 completed May 7, 2026, 8 p.m.
PD Predicate disambiguation batch_69fcecdb97f48190b382b7d13be92dc0 completed May 7, 2026, 7:49 p.m.
PDg Predicate description generation batch_69fcef636dfc819085cf91323f2e4edd completed May 7, 2026, 8 p.m.
Created at: May 1, 2026, 2:02 a.m.