Triple
T28316613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balut Capital of the Philippines |
E717152
|
entity |
| Predicate | isTourismSloganFor |
P25952
|
FINISHED |
| Object | Pateros |
—
|
NE NERFINISHED |
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: Pateros | Statement: [Balut Capital of the Philippines, isTourismSloganFor, Pateros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTourismSloganFor Context triple: [Balut Capital of the Philippines, isTourismSloganFor, Pateros]
-
A.
tourismSlogan
chosen
Indicates that a phrase is used as a promotional slogan to attract tourists to a place or destination.
-
B.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
C.
isTourismBrandName
Indicates that a given name is recognized or used as a brand associated with tourism-related services, products, or destinations.
-
D.
isPopularTouristDestinationIn
Indicates that a place is widely visited and favored by tourists within a specified geographic area or region.
-
E.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f644e8d81881909c9434e133df6bfd |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:21 a.m.