Triple
T37285144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladpura tehsil |
E925510
|
entity |
| Predicate | hasRevenueOffice |
—
|
GENERATED |
| Object | Ladpura tehsil revenue office |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevenueOffice Context triple: [Ladpura tehsil, hasRevenueOffice, Ladpura tehsil revenue office]
-
A.
hasRevenueUnit
Indicates that an entity’s revenue is measured, reported, or associated in terms of a specified unit (e.g., currency or measurement unit).
-
B.
hasSupportingOffice
Indicates that an entity is associated with or served by a particular office that provides support or administrative services to it.
-
C.
hasAssociatedOffice
chosen
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
D.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
E.
hasBackOfficeFunctionsIn
Indicates that an entity’s back-office operations or support functions are performed or located in a specified place or organizational unit.
- F. None of above.
Provenance (1 batch)
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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.