Triple

T38425631
Position Surface form Disambiguated ID Type / Status
Subject Vice Mayor of Manila E903350 entity
Predicate officeHolder P537 FINISHED
Object John Marvin “Yul Servo” Nieto
John Marvin “Yul Servo” Nieto is a Filipino actor-turned-politician known for serving in key local government positions in Manila.
E2269855 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: John Marvin “Yul Servo” Nieto | Statement: [Vice Mayor of Manila, officeHolder, John Marvin “Yul Servo” Nieto]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: John Marvin “Yul Servo” Nieto
Triple: [Vice Mayor of Manila, officeHolder, John Marvin “Yul Servo” Nieto]
Generated description
John Marvin “Yul Servo” Nieto is a Filipino actor-turned-politician known for serving in key local government positions in Manila.

Provenance (5 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_69f76e67e4fc8190a7d08dfe9a8af998 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fccd8eccf08190a774121f4be5a705 completed May 7, 2026, 5:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41c28e35008190b537dfe62747a968 completed June 29, 2026, 12:55 a.m.
NEDg Description generation batch_6a41c3c4ef1c8190a88b7bf1a2b782fa completed June 29, 2026, 1 a.m.
NED2 Entity disambiguation (via description) batch_6a41c6066520819087dbfcda0751628b completed June 29, 2026, 1:10 a.m.
Created at: May 3, 2026, 4:31 p.m.