Triple
T17481654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golasecca III |
E425673
|
entity |
| Predicate | hasMaterialCultureElement |
P86849
|
FINISHED |
| Object | fibulae |
—
|
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: fibulae | Statement: [Golasecca III, hasMaterialCultureElement, fibulae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialCultureElement Context triple: [Golasecca III, hasMaterialCultureElement, fibulae]
-
A.
hasCulturalProduct
Indicates that an entity possesses, produces, or is associated with a cultural artifact, work, or output (such as art, literature, music, or media).
-
B.
hasMaterialResource
Indicates that an entity possesses, controls, or has access to a tangible material resource.
-
C.
hasArchaeologicalMaterial
chosen
Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
-
D.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
-
E.
hasCulturalIcon
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular culture.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bfd75481908c20bc2c1cbff593 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.