Triple
T11852058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President Roxas |
E281930
|
entity |
| Predicate | hasViceChiefExecutiveTitle |
P101858
|
FINISHED |
| Object | Vice Mayor |
—
|
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 | Statement: [President Roxas, hasViceChiefExecutiveTitle, Vice Mayor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViceChiefExecutiveTitle Context triple: [President Roxas, hasViceChiefExecutiveTitle, Vice Mayor]
-
A.
hasViceChairTitle
Indicates that an entity holds the position or bears the formal title of vice chair in relation to another entity or organization.
-
B.
hasChiefTitle
Indicates that an entity holds or is associated with a specific chief-level title or designation within an organization or group.
-
C.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
D.
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).
-
E.
hasMinisterTitle
Indicates that an entity holds or is associated with a specific ministerial title or office.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a696ee548190800d56c64c339b10 |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.