Triple
T24427872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alytus Local History Museum |
E615909
|
entity |
| Predicate | hasMainCollectionSubject |
P106967
|
FINISHED |
| Object | local history of Alytus |
—
|
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: local history of Alytus | Statement: [Alytus Local History Museum, hasMainCollectionSubject, local history of Alytus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCollectionSubject Context triple: [Alytus Local History Museum, hasMainCollectionSubject, local history of Alytus]
-
A.
hasCollectionSubject
chosen
Indicates that a collection is about or thematically centered on a particular subject.
-
B.
hasMainSubjectKey
Indicates that an entity is associated with a primary or principal subject identifier used as its main reference or key.
-
C.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
D.
hasMosaicSubject
Indicates that something is the depicted subject or main theme represented within a mosaic.
-
E.
hasMainRepresentation
Indicates that one entity serves as the primary or canonical representation of 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a84c848190bce2c004a667dbe7 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.