Triple
T38335530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostrog Monastery |
E1037944
|
entity |
| Predicate | visitedAnnuallyBy |
P38405
|
FINISHED |
| Object | hundreds of thousands of pilgrims |
—
|
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: hundreds of thousands of pilgrims | Statement: [Ostrog Monastery, visitedAnnuallyBy, hundreds of thousands of pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedAnnuallyBy Context triple: [Ostrog Monastery, visitedAnnuallyBy, hundreds of thousands of pilgrims]
-
A.
visitYear
Indicates the specific year in which a visit or visitation event took place.
-
B.
annualVisitation
chosen
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
C.
visitedDuring
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
D.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
E.
visitedWith
Indicates that one entity visited a place or another entity together with a companion entity during the same occasion.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.