Triple
T19720373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabanatuan City |
E473591
|
entity |
| Predicate | cityCharterDate |
P8990
|
FINISHED |
| Object | 1950-06-16 |
—
|
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: 1950-06-16 | Statement: [Cabanatuan City, cityCharterDate, 1950-06-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCharterDate Context triple: [Cabanatuan City, cityCharterDate, 1950-06-16]
-
A.
charterDate
chosen
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
B.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
C.
charterEnteredIntoForce
Indicates that a charter has become legally effective and binding as of a specific point in time.
-
D.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
-
E.
hadBoroughCharter
Indicates that an entity was formally granted a borough charter, conferring it the legal status and privileges of a borough.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64410e5548190b60e13603b6c0053 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.