Triple
T5749040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadodara |
E126802
|
entity |
| Predicate | isRegionalCommercialCenterFor |
P64295
|
FINISHED |
| Object | central Gujarat |
—
|
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: central Gujarat | Statement: [Vadodara, isRegionalCommercialCenterFor, central Gujarat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalCommercialCenterFor Context triple: [Vadodara, isRegionalCommercialCenterFor, central Gujarat]
-
A.
isEconomicCenter
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
B.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
C.
isMajorEconomicAreaFor
chosen
Indicates that a location or region serves as a primary center of significant economic activity for a specified entity or sector.
-
D.
isIndustrialCenter
Indicates that a place functions as a major hub of industrial activity, production, or manufacturing within a region.
-
E.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.