Triple
T19523848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Brothers (Riga) |
E488469
|
entity |
| Predicate | oldestBuildingDate |
P136640
|
FINISHED |
| Object | late 15th 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: late 15th century | Statement: [Three Brothers (Riga), oldestBuildingDate, late 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldestBuildingDate Context triple: [Three Brothers (Riga), oldestBuildingDate, late 15th century]
-
A.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
B.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
C.
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.
-
D.
churchConstructionDate
Indicates the date on which a church was constructed or originally built.
-
E.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e636392444819094f6a2aa1cdf3d42 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.