Triple
T21621100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullynally Castle |
E533577
|
entity |
| Predicate | hasPeriodOfExpansion |
P6451
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Tullynally Castle, hasPeriodOfExpansion, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodOfExpansion Context triple: [Tullynally Castle, hasPeriodOfExpansion, 18th century]
-
A.
historicalPeriodOfExpansion
Indicates a historical period during which the referenced entity underwent significant growth, enlargement, or territorial/organizational expansion.
-
B.
timePeriodOfMajorExpansion
chosen
Indicates the time span during which the referenced entity underwent its most significant growth or expansion.
-
C.
hasGeographicExpansion
Indicates that an entity has extended its presence, influence, or operations into additional geographic areas beyond its original location.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
expandedOverTime
Indicates that something has increased in size, scope, or extent as time has passed.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bafef548190b3856bfad1ebdc0b |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.