Triple
T27570154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohapol |
E696010
|
entity |
| Predicate | isOnTourRouteOf |
P17534
|
FINISHED |
| Object | Mehrangarh Fort museum |
—
|
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: Mehrangarh Fort museum | Statement: [Lohapol, isOnTourRouteOf, Mehrangarh Fort museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnTourRouteOf Context triple: [Lohapol, isOnTourRouteOf, Mehrangarh Fort museum]
-
A.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
hasTouringRole
Indicates that an entity holds or performs a specific role or function within a touring context, such as a traveling production, show, or event.
-
C.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
D.
usedOnTour
Indicates that something (such as an item, equipment, or resource) is utilized during a tour or touring activity.
-
E.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62febae708190bc3b9e4dab8c7698 |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:43 p.m.