Triple
T18477657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makati City Hall |
E451473
|
entity |
| Predicate | hasLeaderOffice |
P19057
|
FINISHED |
| Object | Mayor of Makati |
—
|
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: Mayor of Makati | Statement: [Makati City Hall, hasLeaderOffice, Mayor of Makati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeaderOffice Context triple: [Makati City Hall, hasLeaderOffice, Mayor of Makati]
-
A.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
B.
hasAssociatedOffice
chosen
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
C.
hasSupportingOffice
Indicates that an entity is associated with or served by a particular office that provides support or administrative services to it.
-
D.
hasTopOffice
Indicates that an entity holds the highest-ranking office or position within a specified organization, institution, or jurisdiction.
-
E.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53064a7548190b712a14ad0c7a477 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.