Triple

T13087898
Position Surface form Disambiguated ID Type / Status
Subject Pancho E310383 entity
Predicate hasVariant P455 FINISHED
Object Paco E104717 NE 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: Paco | Statement: [Pancho, hasVariant, Paco]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paco
Context triple: [Pancho, hasVariant, Paco]
  • A. Paco
    Paco is a riverside district in Manila, Philippines, known for its historic sites, markets, and dense urban neighborhoods.
  • B. Pascual chosen
    Pascual is a masculine given name of Spanish origin commonly used in Spanish-speaking countries.
  • C. Alfrédo
    Alfrédo is a given name, likely a variant or cognate of "Alfred" or "Alfredo," used as a personal male first name in various languages.
  • D. Ramon
    Ramon is the surname of Ilan Ramon, the first Israeli astronaut and a payload specialist on the Space Shuttle Columbia.
  • E. Ramon
    Ramon is a fictional evolved form or transformation of the character Raginmund, likely appearing in a fantasy or role-playing game setting.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d806a733548190989cfd4ce981ca33 completed April 9, 2026, 8:05 p.m.
NER Named-entity recognition batch_69d981378dd08190b4f00e4e5df0e480 completed April 10, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6d614704481908758cf8691a941ea completed May 3, 2026, 4:59 a.m.
Created at: April 9, 2026, 9:02 p.m.