Triple
T31970966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Aveiro |
E816310
|
entity |
| Predicate | dateOfFirstErection |
P105421
|
FINISHED |
| Object | 1774 |
—
|
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: 1774 | Statement: [Roman Catholic Diocese of Aveiro, dateOfFirstErection, 1774]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstErection Context triple: [Roman Catholic Diocese of Aveiro, dateOfFirstErection, 1774]
-
A.
dateOfCanonicalErection
chosen
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.
-
B.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
-
C.
originallyErectedIn
Indicates that something was first constructed or put up in a specific place or location.
-
D.
oldestBuildingDate
Indicates the calendar date on which the earliest or first-constructed building in a given set or area was built or completed.
-
E.
earliestMajorConstruction
Indicates the earliest significant construction event associated with an entity, such as the first major building or development work completed for it.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 12:10 a.m.