Triple
T4391325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Farriner's bakery |
E99368
|
entity |
| Predicate | destroyedOn |
P5324
|
FINISHED |
| Object | 1666-09-02 |
—
|
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: 1666-09-02 | Statement: [Thomas Farriner's bakery, destroyedOn, 1666-09-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedOn Context triple: [Thomas Farriner's bakery, destroyedOn, 1666-09-02]
-
A.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
dateDestroyed
chosen
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
C.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
D.
traditionallyDestroyedAt
Indicates that something is customarily or historically destroyed at a particular time, place, or event according to tradition.
-
E.
dissipatedOn
Indicates that something (such as energy, force, or a substance) is dispersed, lost, or converted into a less usable form on or within a particular medium, surface, or system.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352843d7c8190929b94c94eaa63df |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.