Triple
T7255216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fernando, Pampanga |
E157700
|
entity |
| Predicate | wasFoundedAsTown |
P75586
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [San Fernando, Pampanga, wasFoundedAsTown, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFoundedAsTown Context triple: [San Fernando, Pampanga, wasFoundedAsTown, 18th century]
-
A.
incorporatedAsTownIn
Indicates that an entity was officially established and given legal status as a town within a specified jurisdiction.
-
B.
foundedAsCounty
Indicates that an administrative region or jurisdiction was originally established with the legal status and designation of a county.
-
C.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
D.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa0c76c81909fe43ed6938a13ea |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:56 p.m.