Triple
T32434107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Beaker culture |
E828808
|
entity |
| Predicate | coreArtifact |
P68510
|
FINISHED |
| Object | bell-shaped drinking vessels |
—
|
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: bell-shaped drinking vessels | Statement: [Bell Beaker culture, coreArtifact, bell-shaped drinking vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreArtifact Context triple: [Bell Beaker culture, coreArtifact, bell-shaped drinking vessels]
-
A.
centralArtifact
Indicates that an artifact serves as the primary or focal object within a given context, structure, or collection.
-
B.
featuresArtifact
Indicates that one entity prominently includes, presents, or showcases another entity as an artifact.
-
C.
testArtifact
Indicates that an entity serves as an artifact or item used for testing, validation, or experimentation in a process or system.
-
D.
majorArtifact
chosen
Indicates that one entity is a primary or highly significant artifact associated with, produced by, or central to the other entity.
-
E.
coreAssembly
Indicates that an entity is responsible for assembling or integrating the central or primary components of another entity into a complete core unit.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b0d31c8190adb202fdf21d4797 |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.