Triple
T13432341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mashhad-e Razavi |
E313642
|
entity |
| Predicate | hasPilgrimVisitorsPerYear |
P45240
|
FINISHED |
| Object | millions of pilgrims annually |
—
|
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: millions of pilgrims annually | Statement: [Mashhad-e Razavi, hasPilgrimVisitorsPerYear, millions of pilgrims annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimVisitorsPerYear Context triple: [Mashhad-e Razavi, hasPilgrimVisitorsPerYear, millions of pilgrims annually]
-
A.
pilgrimsPerYearApprox
chosen
Indicates an approximate number of pilgrims who travel to a place within a year.
-
B.
typicalVisitorsPerSeason
Indicates the usual number of visitors associated with each season for a given entity or location.
-
C.
hasPilgrims
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
-
D.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
E.
pilgrimageFrequency
Indicates how often an entity undertakes or participates in a pilgrimage.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed41a5481908800033303224adb |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.