Triple
T38327840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derngate |
E1036838
|
entity |
| Predicate | hasPeriodArchitecture |
P198208
|
FINISHED |
| Object | Georgian architecture |
—
|
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: Georgian architecture | Statement: [Derngate, hasPeriodArchitecture, Georgian architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodArchitecture Context triple: [Derngate, hasPeriodArchitecture, Georgian architecture]
-
A.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
B.
hasArchitecturalSupport
Indicates that one entity provides structural or design backing, compatibility, or enablement for another within an architectural context.
-
C.
hasSubArchitecture
Indicates that one architectural component or structure is a subordinate or constituent part of a larger overarching architecture.
-
D.
hasPeriods
Indicates that an entity experiences or is characterized by recurring menstrual cycles.
-
E.
hasInfrastructurePeriod
Indicates the time period during which a particular piece of infrastructure exists, is in use, or is valid.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:30 p.m.