Triple
T29318339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballynegall House, County Westmeath |
E743440
|
entity |
| Predicate | hasStyleFeatures |
P144679
|
FINISHED |
| Object | classical proportions |
—
|
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: classical proportions | Statement: [Ballynegall House, County Westmeath, hasStyleFeatures, classical proportions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStyleFeatures Context triple: [Ballynegall House, County Westmeath, hasStyleFeatures, classical proportions]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
C.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
D.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
E.
hasStyleCharacteristics
chosen
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 28, 2026, 1:21 p.m.