Triple
T32204822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Chartreuse monastery |
E822639
|
entity |
| Predicate | hasHermitages |
P192851
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Grande Chartreuse monastery, hasHermitages, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHermitages Context triple: [Grande Chartreuse monastery, hasHermitages, yes]
-
A.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
hasHeritageElements
Indicates that something contains or includes elements that are part of a cultural, historical, or natural heritage.
-
C.
hasHeritageCollections
Indicates that an entity possesses or maintains heritage or historically significant collections.
-
D.
hasCulturalHeritageOn
Indicates that one entity possesses, preserves, or is associated with the cultural heritage embodied in another entity.
-
E.
hasHeritageCenter
Indicates that an entity maintains or is associated with a heritage center dedicated to preserving and presenting cultural or historical heritage.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 1, 2026, 12:36 a.m.