Triple
T18546922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Vues de Manille panoramic wallpaper |
E453258
|
entity |
| Predicate | visualDetail |
P132102
|
FINISHED |
| Object | architectural details of Manila |
—
|
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: architectural details of Manila | Statement: [Les Vues de Manille panoramic wallpaper, visualDetail, architectural details of Manila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualDetail Context triple: [Les Vues de Manille panoramic wallpaper, visualDetail, architectural details of Manila]
-
A.
visualSimplicity
Indicates that something is characterized by a minimal, uncluttered, and easy-to-perceive visual appearance or design.
-
B.
visualImportance
Indicates how visually prominent or attention‑drawing one entity is relative to others in a given context.
-
C.
visionOf
Indicates that one entity is a visual representation, image, or depiction of another entity.
-
D.
visualCenterpiece
Indicates that one entity serves as the primary visual focus or dominant visual element in relation to another entity.
-
E.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534bd0614819083e326d5f22c19ac |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.