Triple
T22667799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solesmes Abbey |
E559837
|
entity |
| Predicate | buildingsSoldAsNationalProperty |
P103896
|
FINISHED |
| Object | 1791 |
—
|
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: 1791 | Statement: [Solesmes Abbey, buildingsSoldAsNationalProperty, 1791]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingsSoldAsNationalProperty Context triple: [Solesmes Abbey, buildingsSoldAsNationalProperty, 1791]
-
A.
lostEstates
chosen
Indicates that one party has lost ownership or control of estates or properties, typically as a result of legal, financial, or political circumstances.
-
B.
buildingOwned
Indicates that one entity possesses legal ownership rights over a building associated with another entity.
-
C.
soldProperty
Indicates that one entity transferred ownership of a property to another entity in exchange for payment.
-
D.
buildingInvolved
Indicates that a particular building participates in, is affected by, or is otherwise relevant to the specified event or relationship.
-
E.
buildingAlsoHouses
Indicates that a building additionally contains or accommodates another function, entity, or activity beyond its primary purpose.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781ceca08190ba1309570e81c5af |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.