Triple
T26695573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pindar Valley |
E673007
|
entity |
| Predicate | accessVillage |
P167100
|
FINISHED |
| Object | Loharkhet |
—
|
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: Loharkhet | Statement: [Pindar Valley, accessVillage, Loharkhet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessVillage Context triple: [Pindar Valley, accessVillage, Loharkhet]
-
A.
typicalAccessVillage
Indicates that the usual or standard way to reach or enter a village is via the specified route or means.
-
B.
hasVillageAccess
Indicates that an entity is permitted to enter, use, or benefit from the facilities, services, or areas of a particular village.
-
C.
accessTown
Indicates that an entity has the ability or permission to enter or make use of a particular town.
-
D.
visitorAccessPoint
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
E.
accessArea
Indicates that an entity is permitted to enter, use, or interact with a specified physical or logical area.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 3:28 a.m.