Triple
T28426104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labhpur |
E720079
|
entity |
| Predicate | hasBlockHeadquarters |
P92824
|
FINISHED |
| Object | Labhpur Community Development Block |
—
|
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: Labhpur Community Development Block | Statement: [Labhpur, hasBlockHeadquarters, Labhpur Community Development Block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlockHeadquarters Context triple: [Labhpur, hasBlockHeadquarters, Labhpur Community Development Block]
-
A.
isBlockHeadquartersOf
chosen
Indicates that a particular block serves as the main headquarters location for a specified entity.
-
B.
hasHigherHeadquarters
Indicates that one organizational unit serves as the superior or parent headquarters overseeing another unit.
-
C.
hasHeadquartersBuilding
Indicates that an organization possesses a specific building that serves as its headquarters location.
-
D.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the specified place.
-
E.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:36 a.m.