Triple
T34284509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | local government of Navotas |
E879695
|
entity |
| Predicate | hasViceLeader |
P101102
|
FINISHED |
| Object | Vice Mayor of Navotas |
—
|
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: Vice Mayor of Navotas | Statement: [local government of Navotas, hasViceLeader, Vice Mayor of Navotas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViceLeader Context triple: [local government of Navotas, hasViceLeader, Vice Mayor of Navotas]
-
A.
hasVicePresidentFor
Indicates that an entity has a specific person or role serving as its vice president for a particular domain, function, or area of responsibility.
-
B.
hasViceChair
Indicates that an entity holds the role or position of vice chair in relation to another entity (such as an organization, committee, or group).
-
C.
hasViceMayor
chosen
Indicates that an entity holds the position of vice mayor for a given administrative or governmental body.
-
D.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
E.
hasViceChiefExecutiveTitle
Indicates that an entity holds the position or role of vice chief executive.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:57 a.m.