Triple
T26748813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Thoronet |
E674475
|
entity |
| Predicate | heritageDesignationOfAbbey |
P623
|
FINISHED |
| Object | historical monument of France |
—
|
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: historical monument of France | Statement: [Le Thoronet, heritageDesignationOfAbbey, historical monument of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageDesignationOfAbbey Context triple: [Le Thoronet, heritageDesignationOfAbbey, historical monument of France]
-
A.
heritageStatusOfAbbey
Indicates the heritage designation or protection status assigned to an abbey.
-
B.
heritageDesignation
chosen
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
C.
heritageDesignationSubject
Indicates that a subject has been assigned a particular heritage designation or status.
-
D.
heritageDesignationVia
Indicates that a heritage designation for an entity is conferred, recorded, or derived through a specific intermediary process, source, or mechanism.
-
E.
churchOfAbbey
Indicates that a given church is associated with, belongs to, or is part of a specified abbey.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:52 a.m.