Triple
T38018738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaya |
E948564
|
entity |
| Predicate | isMajorUrbanCentreIn |
P9892
|
FINISHED |
| Object | Bihar |
—
|
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: Bihar | Statement: [Gaya, isMajorUrbanCentreIn, Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorUrbanCentreIn Context triple: [Gaya, isMajorUrbanCentreIn, Bihar]
-
A.
isMajorCityIn
chosen
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
B.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
C.
nearestLargeUrbanArea
Indicates that one entity is the closest major city or large urban center to the other entity.
-
D.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
E.
isAdministrativeCenterIn
Indicates that an entity serves as the main administrative or governmental center located within a specified larger area or jurisdiction.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:20 p.m.