Triple
T35879062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loudoun Castle |
E1037456
|
entity |
| Predicate | postFireCondition |
P183937
|
FINISHED |
| Object | partly ruined |
—
|
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: partly ruined | Statement: [Loudoun Castle, postFireCondition, partly ruined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postFireCondition Context triple: [Loudoun Castle, postFireCondition, partly ruined]
-
A.
postFireUse
Indicates how something is used, managed, or occupied after a fire has occurred.
-
B.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
C.
postUse
Indicates that one entity is used or occurs after another entity has been used or has taken place.
-
D.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
E.
postEventStatus
Indicates the status or condition assigned to an event after it has occurred or been processed.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.