Triple
T4563389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnapore |
E121849
|
entity |
| Predicate | hasPINCodePrefix |
P961
|
FINISHED |
| Object | 721 |
—
|
LITERAL 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: 721 | Statement: [Midnapore, hasPINCodePrefix, 721]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPINCodePrefix Context triple: [Midnapore, hasPINCodePrefix, 721]
-
A.
hasPINCode
Indicates that an entity is associated with or assigned a specific personal identification number (PIN) code.
-
B.
hasPostalCodePrefix
chosen
Indicates that a location’s postal code begins with a specified sequence of characters.
-
C.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
D.
hasAirportCodePrefix
Indicates that an airport’s code begins with a specified sequence of characters.
-
E.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd5830b4308190a63699bf28922375 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.