Triple
T36627694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compostela Valley |
E904220
|
entity |
| Predicate | ratificationOfRename |
P60794
|
FINISHED |
| Object | 2020-03-07 |
—
|
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: 2020-03-07 | Statement: [Compostela Valley, ratificationOfRename, 2020-03-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratificationOfRename Context triple: [Compostela Valley, ratificationOfRename, 2020-03-07]
-
A.
officialRenaming
chosen
Indicates that an entity has been given a new official name, formally replacing its previous designation.
-
B.
renamingAuthority
Indicates that the subject has the authority or power to change the name or designation of the object.
-
C.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
D.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
E.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.