Triple
T25891967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leach pottery tradition |
E652357
|
entity |
| Predicate | typicalFiring |
P75588
|
FINISHED |
| Object | reduction 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: reduction firing | Statement: [Leach pottery tradition, typicalFiring, reduction firing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFiring Context triple: [Leach pottery tradition, typicalFiring, reduction firing]
-
A.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
-
B.
firingCharacteristic
chosen
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
-
C.
firingDetail
Indicates that one entity performs or is involved in a specific act of firing (such as discharging a weapon or initiating a shot) toward or in relation to another entity, including contextual details of that firing event.
-
D.
firingPurpose
Indicates the reason or intended objective behind initiating a firing or discharge action.
-
E.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 22, 2026, 8:22 a.m.