Triple
T27719340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTB Nagar |
E698907
|
entity |
| Predicate | fullFormOfName |
P161411
|
FINISHED |
| Object | Guru Tegh Bahadur Nagar |
—
|
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: Guru Tegh Bahadur Nagar | Statement: [GTB Nagar, fullFormOfName, Guru Tegh Bahadur Nagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullFormOfName Context triple: [GTB Nagar, fullFormOfName, Guru Tegh Bahadur Nagar]
-
A.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
fullGivenNameOf
chosen
Indicates that one entity is the complete, formal given name corresponding to another entity (such as a person or identifier).
-
C.
acronymExpansion
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
D.
fullLegalName
Indicates that the associated value is the complete, official legal name of the entity as recognized by law or formal records.
-
E.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6363a71e88190a2df9d30f527154d |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:06 p.m.