Triple
T34913926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Baltic barrow culture |
E1006948
|
entity |
| Predicate | funeraryMonumentType |
P133766
|
FINISHED |
| Object | barrow |
—
|
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: barrow | Statement: [Western Baltic barrow culture, funeraryMonumentType, barrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funeraryMonumentType Context triple: [Western Baltic barrow culture, funeraryMonumentType, barrow]
-
A.
hasBurialMonumentType
chosen
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
B.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
C.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
D.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
-
E.
tombDecoration
Indicates that something serves as an ornamental or symbolic adornment associated with a tomb.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.