Triple
T16360492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balagtas |
E397296
|
entity |
| Predicate | hasHistoricalNameChangeReason |
P123115
|
FINISHED |
| Object | to honor Francisco Balagtas |
—
|
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: to honor Francisco Balagtas | Statement: [Balagtas, hasHistoricalNameChangeReason, to honor Francisco Balagtas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalNameChangeReason Context triple: [Balagtas, hasHistoricalNameChangeReason, to honor Francisco Balagtas]
-
A.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
B.
hasHistoricNameVariant
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
C.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
D.
hasHistoricNickname
Indicates that an entity is known by a nickname that has historical significance or longstanding traditional use.
-
E.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2fad241848190a9f32c7b050f20a5 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.