Triple
T25579414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Pierre Abbey (Moissac) |
E641198
|
entity |
| Predicate | hasCloisterConstructionDate |
P65756
|
FINISHED |
| Object | early 12th century |
—
|
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: early 12th century | Statement: [Saint-Pierre Abbey (Moissac), hasCloisterConstructionDate, early 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloisterConstructionDate Context triple: [Saint-Pierre Abbey (Moissac), hasCloisterConstructionDate, early 12th century]
-
A.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
-
B.
hasCloisterFromCentury
chosen
Indicates that an entity possesses a cloister that dates from, or was constructed in, a specified century.
-
C.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
D.
cloisterConstruction
Indicates the construction or building activity specifically related to a cloister or cloistered architectural space.
-
E.
hasCloisterWalls
Indicates that something possesses or is surrounded by cloister walls as an architectural feature.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 4:04 p.m.