Triple

T17449483
Position Surface form Disambiguated ID Type / Status
Subject Municipality of Carlos P. Garcia, Bohol E424874 entity
Predicate hasNamingReason P7885 FINISHED
Object to honor Carlos P. Garcia’s legacy 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: to honor Carlos P. Garcia’s legacy | Statement: [Municipality of Carlos P. Garcia, Bohol, hasNamingReason, to honor Carlos P. Garcia’s legacy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNamingReason
Context triple: [Municipality of Carlos P. Garcia, Bohol, hasNamingReason, to honor Carlos P. Garcia’s legacy]
  • A. hasNaming
    Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
  • B. reasonForName chosen
    Indicates the explanation or cause behind why an entity has a particular name.
  • C. hasNameGivenTo
    Indicates that one entity is the name that has been assigned or given to another entity.
  • D. usesNameDueTo
    Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
  • E. namedAccordingTo
    Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
  • 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_69d889db0ba481908402409af3b37917 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4513b99908190a6b5833559856c8b completed April 19, 2026, 3:51 a.m.
PD Predicate disambiguation batch_69e3b4f0e3fc819094e466b74622c956 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:47 a.m.