Triple
T27421244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lasta |
E693048
|
entity |
| Predicate | religiousArchitecturePeriod |
P103862
|
FINISHED |
| Object | 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: 12th century | Statement: [Lasta, religiousArchitecturePeriod, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousArchitecturePeriod Context triple: [Lasta, religiousArchitecturePeriod, 12th century]
-
A.
timePeriodOfArchitecture
chosen
Indicates the historical time period or era during which a particular architectural work, style, or feature was created or predominantly used.
-
B.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
C.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
-
D.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
E.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 12:36 p.m.