Triple
T27799655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghorepani Poon Hill |
E702204
|
entity |
| Predicate | typicalStopover |
P138842
|
FINISHED |
| Object | Ghorepani village |
—
|
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: Ghorepani village | Statement: [Ghorepani Poon Hill, typicalStopover, Ghorepani village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStopover Context triple: [Ghorepani Poon Hill, typicalStopover, Ghorepani village]
-
A.
typicalStopoverCity
Indicates that a city commonly serves as an intermediate stop or layover point in a journey between other locations.
-
B.
typicalStopoverRegion
Indicates the geographic region where an entity (such as a migrating animal or traveler) most commonly makes an intermediate stop during its journey.
-
C.
typicalOvernightStop
Indicates that a location is commonly used as an overnight stopping point along a route or journey.
-
D.
aircraftStopover
Indicates that an aircraft makes an intermediate stop at a specific location during its journey between origin and final destination.
-
E.
stopoverLocation
chosen
Indicates that an entity makes an intermediate stop or layover at a specified location during a journey or route.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: April 27, 2026, 5:33 p.m.