Triple
T8686171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varna Archaeological Museum |
E206164
|
entity |
| Predicate | holdsCollection |
P426
|
FINISHED |
| Object | Varna Necropolis artifacts |
—
|
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: Varna Necropolis artifacts | Statement: [Varna Archaeological Museum, holdsCollection, Varna Necropolis artifacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsCollection Context triple: [Varna Archaeological Museum, holdsCollection, Varna Necropolis artifacts]
-
A.
heldMany
Indicates that one entity has possessed or maintained control over a large number or quantity of another entity over time.
-
B.
hasCollection
chosen
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
C.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
D.
holdingType
Indicates the type or category of a holding or possession that one entity has in relation to another or to an asset.
-
E.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aec1f8c8190a9ab1a73c2dbcd3c |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.