Triple
T35749314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchy |
E1033272
|
entity |
| Predicate | historicBuildingDate |
P202792
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Buchy, historicBuildingDate, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicBuildingDate Context triple: [Buchy, historicBuildingDate, 17th century]
-
A.
oldestBuildingDate
Indicates the calendar date on which the earliest or first-constructed building in a given set or area was built or completed.
-
B.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
C.
churchConstructionDate
Indicates the date on which a church was constructed or originally built.
-
D.
originallyErectedIn
Indicates that something was first constructed or put up in a specific place or location.
-
E.
dateOfCanonicalErection
Indicates the official date on which an institution, organization, or entity was formally and canonically established or erected according to relevant legal or religious norms.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
| PDg | Predicate description generation | batch_6a00bb39c9c88190b82c8a8fb6489a61 |
completed | May 10, 2026, 5:07 p.m. |
Created at: May 3, 2026, 4:06 p.m.