Triple
T19363397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rupbas |
E484336
|
entity |
| Predicate | nearbyType |
P75188
|
FINISHED |
| Object | religious pilgrimage centers |
—
|
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: religious pilgrimage centers | Statement: [Rupbas, nearbyType, religious pilgrimage centers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyType Context triple: [Rupbas, nearbyType, religious pilgrimage centers]
-
A.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyFacilityType
chosen
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a897008190a2c62a50ca60de2d |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.