Triple
T26221681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehatta |
E655778
|
entity |
| Predicate | postalSystemUsed |
P90695
|
FINISHED |
| Object | India Post |
—
|
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: India Post | Statement: [Tehatta, postalSystemUsed, India Post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalSystemUsed Context triple: [Tehatta, postalSystemUsed, India Post]
-
A.
hasPostalSystem
Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
-
B.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
C.
postalCodeSystem
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
D.
hasPostalSystemOf
Indicates that one entity possesses, uses, or is characterized by the postal system belonging to another entity.
-
E.
hasPostalServiceThrough
chosen
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d5060708190b3134a5e5a4ca850 |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:56 p.m.