Triple
T28850459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soanian culture |
E728577
|
entity |
| Predicate | toolManufacturingTechnique |
P3047
|
FINISHED |
| Object | direct hard-hammer percussion |
—
|
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: direct hard-hammer percussion | Statement: [Soanian culture, toolManufacturingTechnique, direct hard-hammer percussion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolManufacturingTechnique Context triple: [Soanian culture, toolManufacturingTechnique, direct hard-hammer percussion]
-
A.
fabricationTechnology
Indicates the manufacturing or production method used to create or realize an entity.
-
B.
metalworkingProduct
Indicates that one entity is a product or outcome resulting from the metalworking activities or processes performed on another entity.
-
C.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
D.
artisticTechnique
Indicates the method, style, or process used to create or execute an artistic work.
-
E.
toolMorphology
Indicates a relationship where one entity’s form, structure, or physical configuration functions as or defines it as a tool for another entity or purpose.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d855b4819099e9c239051edafe |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:43 a.m.