Triple
T37252531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaça de Colom |
E924030
|
entity |
| Predicate | hasPrimaryMonumentSubject |
P198121
|
FINISHED |
| Object | Christopher Columbus statue |
E264779
|
NE 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: Christopher Columbus statue | Statement: [Plaça de Colom, hasPrimaryMonumentSubject, Christopher Columbus statue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryMonumentSubject Context triple: [Plaça de Colom, hasPrimaryMonumentSubject, Christopher Columbus statue]
-
A.
hasPrimaryMonument
Indicates that an entity is associated with its main or most significant monument.
-
B.
hasMonumentFunction
Indicates that something serves the role or purpose of a monument, such as commemorating, honoring, or symbolizing a person, event, or idea.
-
C.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
-
D.
hasMonumentAt
chosen
Indicates that a monument is located at or associated with a specific place or site.
-
E.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
- F. None of above.
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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a405128946481909a5f05234d9855d4 |
completed | June 27, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.