Triple
T32453409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noida Sector 15 |
E829356
|
entity |
| Predicate | abbreviationOfCityName |
P62925
|
FINISHED |
| Object | New Okhla Industrial Development Authority |
—
|
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: New Okhla Industrial Development Authority | Statement: [Noida Sector 15, abbreviationOfCityName, New Okhla Industrial Development Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfCityName Context triple: [Noida Sector 15, abbreviationOfCityName, New Okhla Industrial Development Authority]
-
A.
cityAbbreviationOf
chosen
Indicates that one term is an official or commonly used abbreviated form of the name of a particular city.
-
B.
portAbbreviation
Indicates that one port is an abbreviated or shortened form of another port’s name or designation.
-
C.
cityNicknameAssociation
Indicates an associative relationship where a particular nickname is used to refer to or characterize a specific city.
-
D.
cityNickname
Indicates that one entity is commonly used as an informal or alternative name for a city.
-
E.
eraAbbreviation
Indicates that one term is the standard shortened or abbreviated form of a named historical or chronological era.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 12:56 a.m.