Triple
T4654985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grimsthorpe Castle |
E102385
|
entity |
| Predicate | hasBuildingComponent |
P58239
|
FINISHED |
| Object | courtyard |
—
|
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: courtyard | Statement: [Grimsthorpe Castle, hasBuildingComponent, courtyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingComponent Context triple: [Grimsthorpe Castle, hasBuildingComponent, courtyard]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
C.
hasBuildingForm
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
-
D.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
E.
hasBuildingPattern
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6317ba70819089145766d3462e57 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:14 p.m.