Triple
T19737132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Palacio |
E474014
|
entity |
| Predicate | isMonumental |
P6202
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Le Palacio, isMonumental, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonumental Context triple: [Le Palacio, isMonumental, true]
-
A.
hasMonumentalFeature
Indicates that an entity possesses or includes a significant, large-scale, or historically important physical feature or structure.
-
B.
isMonumentClassic
Indicates that a monument exemplifies classic or traditional architectural or historical style.
-
C.
isMonumentalTree
Indicates that a tree is officially recognized as exceptionally significant, typically due to its age, size, rarity, historical, cultural, or ecological importance.
-
D.
significantMonument
chosen
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
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 (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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515ea688819097b6838e6a3b3d4a |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.