Triple
T25133492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solutrean archaeological culture |
E629591
|
entity |
| Predicate | hasLithicTechnology |
P86842
|
FINISHED |
| Object | bifacial leaf points |
—
|
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: bifacial leaf points | Statement: [Solutrean archaeological culture, hasLithicTechnology, bifacial leaf points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLithicTechnology Context triple: [Solutrean archaeological culture, hasLithicTechnology, bifacial leaf points]
-
A.
lithicTechnology
chosen
Indicates the use, production, or study of stone-based tools and technologies within a given context.
-
B.
hasArchaeologicalMaterial
Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
-
C.
hasArchaeologicalCulture
Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
-
D.
hasNearbyAncientCulture
Indicates that one entity is geographically close to another entity associated with an ancient culture or civilization.
-
E.
hasArchaeologicalFeature
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:28 a.m.