Triple
T7090751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delftware ceramics |
E165186
|
entity |
| Predicate | firingProcess |
P4106
|
FINISHED |
| Object | biscuit firing |
—
|
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: biscuit firing | Statement: [Delftware ceramics, firingProcess, biscuit firing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingProcess Context triple: [Delftware ceramics, firingProcess, biscuit firing]
-
A.
durationOfFiring
Indicates the length of time that a firing event or process continues.
-
B.
designedToFire
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
-
C.
firingDirection
Indicates the direction or trajectory along which a firing action (such as shooting or launching a projectile) is aimed or executed.
-
D.
partOfProcess
chosen
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
E.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e53012b081908bf40541d85c82f1 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.