Triple
T767139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza Mayor de Lima |
E16199
|
entity |
| Predicate | languageOfSurroundingSignage |
P4196
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Plaza Mayor de Lima, languageOfSurroundingSignage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSurroundingSignage Context triple: [Plaza Mayor de Lima, languageOfSurroundingSignage, Spanish]
-
A.
languageOfSignage
chosen
Indicates the language used on signs or written displays associated with an entity.
-
B.
tertiaryLanguageOfSignage
Indicates that a language is used as the third-most prominent language on signage in a given context or location.
-
C.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
D.
languageOfOfficialGuides
Indicates the language in which official guides or instructional materials are provided or published.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.