Triple
T26224906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangladesh Monastery |
E655862
|
entity |
| Predicate | servesPilgrimsFrom |
P57386
|
FINISHED |
| Object | Bangladesh |
—
|
NE NERFINISHED |
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: Bangladesh | Statement: [Bangladesh Monastery, servesPilgrimsFrom, Bangladesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPilgrimsFrom Context triple: [Bangladesh Monastery, servesPilgrimsFrom, Bangladesh]
-
A.
pilgrimsFrom
chosen
Indicates that one or more pilgrims originate from, or are associated with coming from, a particular place.
-
B.
hasPilgrims
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
-
C.
pilgrimsObtain
Indicates that pilgrims acquire, receive, or come into possession of something.
-
D.
servesPilgrimTrafficTo
Indicates that a location or entity functions as a route, hub, or provider facilitating the movement or flow of pilgrim traffic to a specified destination.
-
E.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 26, 2026, 8:57 p.m.