Triple
T19950131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarka–Somnath–Girnar circuit |
E479531
|
entity |
| Predicate | notableSiteType |
P137964
|
FINISHED |
| Object | coastal city |
—
|
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: coastal city | Statement: [Dwarka–Somnath–Girnar circuit, notableSiteType, coastal city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSiteType Context triple: [Dwarka–Somnath–Girnar circuit, notableSiteType, coastal city]
-
A.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
B.
notableSiteAssociatedWith
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
E.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
- F. None of above. chosen
Provenance (4 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6a93548190875af2176e6901a7 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.