Triple
T6497617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPoM |
E148796
|
entity |
| Predicate | titleAcronymOf |
P28332
|
FINISHED |
| Object | Informe de Política Monetaria |
—
|
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: Informe de Política Monetaria | Statement: [IPoM, titleAcronymOf, Informe de Política Monetaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAcronymOf Context triple: [IPoM, titleAcronymOf, Informe de Política Monetaria]
-
A.
titlePhrase
Indicates that one entity is a phrase functioning as the title or name of another entity.
-
B.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
C.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
D.
titleVariant
chosen
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
E.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:41 p.m.