Triple
T37285144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladpura tehsil |
E925510
|
entity |
| Predicate | hasRevenueOffice |
P19057
|
FINISHED |
| Object | Ladpura tehsil revenue office |
E925510
|
NE 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: Ladpura tehsil revenue office | Statement: [Ladpura tehsil, hasRevenueOffice, Ladpura tehsil revenue office]
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 (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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40513fda208190bc69efd7751ebe28 |
completed | June 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.