Triple
T16088717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Windsor Castle fire |
E390301
|
entity |
| Predicate | timeToBringUnderControl |
P84252
|
FINISHED |
| Object | approximately 15 hours |
—
|
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: approximately 15 hours | Statement: [1992 Windsor Castle fire, timeToBringUnderControl, approximately 15 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToBringUnderControl Context triple: [1992 Windsor Castle fire, timeToBringUnderControl, approximately 15 hours]
-
A.
timeToControl
chosen
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
B.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
-
C.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
D.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
E.
timeHorizonOfImpact
Indicates the span of time over which an action, event, or factor is expected to produce its effects or consequences.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.