Triple
T38701982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panay, Capiz |
E950162
|
entity |
| Predicate | isFormerProvincialCapital |
P3417
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Panay, Capiz, isFormerProvincialCapital, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerProvincialCapital Context triple: [Panay, Capiz, isFormerProvincialCapital, true]
-
A.
capitalOfProvincePreviouslyLocatedOn
Indicates that an entity serves or served as the capital city of a province that was formerly situated in a specified location.
-
B.
isProvincialCapital
Indicates that a location serves as the administrative capital of a province within a country or region.
-
C.
isInFormerCapital
Indicates that an entity is located within a city that previously served as a capital but no longer holds that status.
-
D.
usedToBeSeatOf
Indicates that an entity previously served as the official seat or administrative center of another entity, but no longer holds that status.
-
E.
formerCapitalOf
chosen
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.